Re: ecpg and bison again - Mailing list pgsql-hackers

From Michael Meskes
Subject Re: ecpg and bison again
Date
Msg-id 20020621145412.GD9574@feivel.fam-meskes.de
Whole thread Raw
In response to Re: ecpg and bison again  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Jun 19, 2002 at 10:14:32AM -0400, Tom Lane wrote:
> I agree it's not pleasant to be blocked like this.  Is there any way we
> can persuade the bison guys to be a little more urgent about releasing a
> fix?  (If 1.49 is just an internal beta version, maybe a back-patch to
> their last released version?)

I had the feeling they rewrote some major parts. You cannot back-patch
that. But then I may err on this.

> Another possibility is to temporarily disable ecpg from being built by
> default (eg, just remove it from src/interfaces/Makefile) and then go
> ahead and commit your changes.  Then, anyone wanting to test it would
> have to (a) have a suitable bison installed and (b) manually go into
> interfaces/ecpg and say "make all install".  I can't say that I like
> this idea, but it seems better than putting derived files into CVS.

That would be possible too.

> PS: BTW, are any of the bison people at Red Hat?  Maybe I could apply
> a little internal pressure...

No idea, sorry.

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: What is wrong with hashed index usage?
Next
From: Rod Taylor
Date:
Subject: Problems with dump /restore of views