Michael Meskes <meskes@postgreSQL.org> writes:
> On Sun, Mar 07, 1999 at 02:22:28PM -0500, Tom Lane wrote:
>> Wait a sec ... ecpg? ecpg shouldn't be depending on backend internals
>> at all, should it? I thought we were talking about support for
>> dynamically loaded backend extensions.
> Hmm, historically ecpg's ecpglib.h includes postgres.h which include
> palloc.h. But scanning through postgres.h I wonder why.
It'd probably be better if you could make ecpg code depend only on
postgres_ext.h. However, I did commit fixes yesterday to solve the
immediate problem with mcxt.h.
regards, tom lane