"Marko Kreen" <[EMAIL PROTECTED]> writes:
> How about following patch?  I have bison 2.3 and it seems not to do
> global allocation, so it should be fine.  There may be early exit
> with elog(ERRROR) inside so I'd like to avoid malloc() itself.

None of our other parsers fool with bison's memory allocation;
why does yours need to?

                        regards, tom lane

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to