Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
> Tom Lane wrote:
>> Why in the world is ecpg including either primnodes.h or postgres.h?
> The problem is that ecpg shares parser.c source code and this code
> includes postgres.h.
ecpg cannot do that. It would fail if parser.c happened to use anything
that won't compile in frontend, eg elog() or palloc(). It's mere luck
that it's worked for him so far.
Considering that ecpg has its own copy of all of gram.y and scan.l,
sharing parser.c isn't much of a savings anyway.
regards, tom lane
