Re: bison news

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bison news
Date: 2002-08-20 20:30:07
Message-ID: 200208202030.g7KKU7S02649@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


OK, now that _a_ bison exists that works, how does this effect our
release? I don't see preproc.[ch] in CVS. Do we need this new bison
version on postgresql.org because Marc generates these as part of his
install script?

---------------------------------------------------------------------------

Tom Lane wrote:
> 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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2002-08-20 20:31:50 Re: @(#)Mordred Labs advisory 0x0003: Buffer overflow in PostgreSQL (fwd)
Previous Message Tom Lane 2002-08-20 20:21:50 Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in