| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(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 04:45:06 |
| Message-ID: | 24959.1031719506@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
I am also still wondering if we couldn't tweak the grammar to eliminate
states so that ecpg would build with a standard bison. That would be a
win all 'round, but it requires effort that we maybe don't have to
spend.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2002-09-11 04:56:59 | Re: 7.3beta and ecpg |
| Previous Message | Bruce Momjian | 2002-09-11 04:42:16 | Re: Please rename split(text,text,int) to splitpart |