From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <hackers(at)postgresql(dot)org> |
Subject: | Re: new yacc problem |
Date: | 1998-02-05 02:01:59 |
Message-ID: | 34D91D97.BA3980B7@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Here is what I get from the current cvsup:
>
> ---------------------------------------------------------------------------
>
> /usr/bin/yacc -d gram.y
> /usr/bin/yacc: f - maximum table size exceeded
> gmake[2]: *** [parse.h] Error 2
> gmake[2]: Leaving directory `/usr/local/src/pgsql/pgsql/src/backend/parser'
> gmake[1]: *** [parser.dir] Error 2
> gmake[1]: Leaving directory `/usr/local/src/pgsql/pgsql/src/backend'
> gmake: *** [all] Error 2
Uh oh. Are there any switches on yacc which would let you increase some
internal parameters?
If not, we could try delivering gram.c as we do with scan.c. With the current
parser scheme, I don't see how we could shrink things very much :<(
- Tom
I haven't yet tested with both our our recent changes in; will let you know if
bison has trouble...
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas G. Lockhart | 1998-02-05 02:25:02 | Re: [HACKERS] Error in select |
Previous Message | Thomas G. Lockhart | 1998-02-05 01:52:08 | Re: [HACKERS] Re: [QUESTIONS] is Postgres an SQL-based database? |