Re: new yacc problem - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: new yacc problem
Date
Msg-id 199802050327.WAA11235@candle.pha.pa.us
Whole thread Raw
In response to Re: new yacc problem  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
List 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?

Nope.  I don't see any.

> 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 :<(

Would be a good idea.

> I haven't yet tested with both our our recent changes in; will let you know if
> bison has trouble...

Got bison.  Works fine.

--
Bruce Momjian
maillist@candle.pha.pa.us

pgsql-hackers by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [HACKERS] User-defined functions with NULL values and sets as parameter and/or return type
Next
From: The Hermit Hacker
Date:
Subject: Re: [HACKERS] snapshot won't compile on irix6.2