| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Meskes <meskes(at)postgresql(dot)org>, PostgreSQL Hacker <pgsql-hackers(at)postgresql(dot)org>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Subject: | Re: 7.3beta and ecpg |
| Date: | 2002-09-11 05:39:04 |
| Message-ID: | 200209110539.g8B5d4421151@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > We will not find out if there are problems with the bison beta until we
> > ship it as part of beta and I don't think we have to be scared of just
> > because it is beta.
>
> No? If there are bugs in it, they will break the main SQL parser, not
> only ecpg. I am scared.
>
> My idea of a reasonable fallback is to add prebuilt-with-the-beta-bison
> output files to the ecpg directory, but not anyplace else. That is
> ugly, but the effects of any bison problems will be limited to ecpg.
Yes, I assumed we would use the new bison only for ecpg.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2002-09-11 05:47:25 | Re: Script to compute random page cost |
| Previous Message | Joe Conway | 2002-09-11 05:05:45 | Re: Please rename split(text,text,int) to splitpart |