| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Meskes <meskes(at)postgresql(dot)org> |
| Cc: | PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: bison news |
| Date: | 2002-08-20 15:32:52 |
| Message-ID: | 6822.1029857572@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Meskes <meskes(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-20 15:37:18 | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow |
| Previous Message | Tom Lane | 2002-08-20 15:28:32 | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in |