interfaces/ecpg/preproc reduce/reduce conflicts

Started by Joe Conwayover 23 years ago7 messages
#1Joe Conway
mail@joeconway.com

Just noticed this a few minutes ago on build from cvs tip:

make -C preproc all
make[4]: Entering directory `/opt/src/pgsql/src/interfaces/ecpg/preproc'
bison -y -d preproc.y
conflicts: 2 reduce/reduce

Joe

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Joe Conway (#1)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

Joe Conway <mail@joeconway.com> writes:

Just noticed this a few minutes ago on build from cvs tip:
make -C preproc all
make[4]: Entering directory `/opt/src/pgsql/src/interfaces/ecpg/preproc'
bison -y -d preproc.y
conflicts: 2 reduce/reduce

Yeah, the ECPG grammar has been broken for awhile. I'm expecting
Michael to do something about it sooner or later ...

regards, tom lane

#3Alvaro Herrera
alvherre@atentus.com
In reply to: Tom Lane (#2)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

On Thu, 16 May 2002, Tom Lane wrote:

Joe Conway <mail@joeconway.com> writes:

Just noticed this a few minutes ago on build from cvs tip:
make -C preproc all
make[4]: Entering directory `/opt/src/pgsql/src/interfaces/ecpg/preproc'
bison -y -d preproc.y
conflicts: 2 reduce/reduce

Yeah, the ECPG grammar has been broken for awhile. I'm expecting
Michael to do something about it sooner or later ...

It's not just the grammar. Last time I tried to compile OSDB to get some
benchmarking done, ecpg segfaulted on it (before having any reduce
conflict). I tried to do some investigation, but my knowledge was too
limited and couldn't even generate a decent bug report.

--
Alvaro Herrera (<alvherre[@]dcc.uchile.cl>)
"Nunca se desea ardientemente lo que solo se desea por razon" (F. Alexandre)

#4Michael Meskes
meskes@postgresql.org
In reply to: Joe Conway (#1)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

On Thu, May 16, 2002 at 04:51:28PM -0700, Joe Conway wrote:

make -C preproc all
make[4]: Entering directory `/opt/src/pgsql/src/interfaces/ecpg/preproc'
bison -y -d preproc.y
conflicts: 2 reduce/reduce

Didn't notice this before. Fix was quite easy, but I also did sync
ecpg's parser with the backend one and now I cannot compile it anymore.
Haven't found time to dig into this. So be careful, current CVS WILL NOT
COMPILE!

This is what happens:

preproc.y:5330: fatal error: maximum table size (32767) exceeded

I never before saw that and didn't find it in the docs with a quick
grep. Maybe someone knows this. Else I will check in more detail.

Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

#5Michael Meskes
meskes@postgresql.org
In reply to: Alvaro Herrera (#3)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

On Fri, May 17, 2002 at 10:47:54AM -0400, Alvaro Herrera wrote:

It's not just the grammar. Last time I tried to compile OSDB to get some
benchmarking done, ecpg segfaulted on it (before having any reduce
conflict). I tried to do some investigation, but my knowledge was too
limited and couldn't even generate a decent bug report.

But at least you could send me a mail telling me something fails. :-)

I won't debug this if I don't know it fails.

Michael

--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!

#6Tom Lane
tgl@sss.pgh.pa.us
In reply to: Michael Meskes (#4)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

Michael Meskes <meskes@postgresql.org> writes:

Haven't found time to dig into this. So be careful, current CVS WILL NOT
COMPILE!

If you're not going to fix it right away, would you mind reverting the
commit?

regards, tom lane

#7Michael Meskes
meskes@postgresql.org
In reply to: Tom Lane (#6)
Re: interfaces/ecpg/preproc reduce/reduce conflicts

On Sun, May 19, 2002 at 04:19:58PM -0400, Tom Lane wrote:

Michael Meskes <meskes@postgresql.org> writes:

Haven't found time to dig into this. So be careful, current CVS WILL NOT
COMPILE!

If you're not going to fix it right away, would you mind reverting the
commit?

Sorry, I just found this mail, no idea where it stuck since sunday.
Don't worry, it's already fixed.

Also I'm in contact with some bison developers.

Michael
--
Michael Meskes
Michael@Fam-Meskes.De
Go SF 49ers! Go Rhein Fire!
Use Debian GNU/Linux! Use PostgreSQL!