Michael Meskes <meskes@postgresql.org> writes:
> On Thu, Oct 25, 2007 at 11:31:15AM -0400, Tom Lane wrote:
>> 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.
> No, actually it's the first step at making ecpg use all the backend
> files instead. I would prefer to get away from all those manual syncing.
Well, that's surely a good idea, but there'll have to be some
negotiation to figure out how to do that. None of those files are
currently designed with any thought of being compilable outside the
backend environment.
The hard part really would be sharing gram.y and scan.l, especially in
view of the fact that we need different actions. Do you have a plan
for doing that?
regards, tom lane
