Re: [COMMITTERS] pgsql/src/interfaces/ecpg ChangeLog preproc/ec ...

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: [COMMITTERS] pgsql/src/interfaces/ecpg ChangeLog preproc/ec ...
Date: 2002-05-20 14:31:57
Message-ID: 22384.1021905117@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Michael Meskes <meskes(at)postgresql(dot)org> writes:
> [Moved to hackers}
> On Sun, May 19, 2002 at 04:14:47PM -0400, Tom Lane wrote:
>> preproc.y:5330: fatal error: maximum table size (32767) exceeded
>>
>> This is with
>> $ bison -V
>> GNU Bison version 1.28

> I'm using bison 1.35, but get the same error.

1.35? Sounds like bison development has become active again. It was
stuck at 1.28 for a *long* time.

> It seems that there are only one or two projects ever to hit that limit.
> But it appears to be a hardcoded limit inside bison. It seems I hit that
> limit with the latest changes.
> Right now I'm removing some simple rules to get under it again, but we
> will certainly hit it again in the very near future.

Yes. Maybe we should contact the Bison developers and lobby for an
increase in the standard value. I don't mind saying "you must use
Bison 1.36 or newer to rebuild the Postgres grammar" ... but having to
say "you must use a nonstandardly patched Bison" would really suck :-(

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian - CVS 2002-05-20 22:22:27 pgsql/doc TODO
Previous Message Michael Meskes 2002-05-20 09:29:41 pgsql/src/interfaces/ecpg ChangeLog preproc/c_ ...

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-05-20 15:05:38 Re: Unbounded (Possibly) Database Size Increase - Toasting
Previous Message Hannu Krosing 2002-05-20 14:27:59 Re: Unbounded (Possibly) Database Size Increase - Toasting