Michael Meskes <meskes@postgresql.org> writes:
> On Tue, Aug 20, 2002 at 11:10:01AM -0400, Tom Lane wrote:
>> BTW, I spent some time looking at the problem, and it seems the issue
>> is not overrun of any bison internal table, but failure to compress the
>> resulting "action table" into 32K entries. This means that the required
> Ouch! This of course is not so much a problem for ecpg but for the
> backend should we run into the problem there too.
As of CVS tip a few days ago, the backend's action table was about 27K
entries. So we have some breathing room, but certainly in the
foreseeable future there will be a problem...
regards, tom lane
