I had a thought about what to do with the ECPG grammar-too-big problem:
rather than depending on a beta release of bison, we could attack the
problem directly by omitting some of the backend grammar from what ECPG
supports. Surely there are not many people using ECPG to issue obscure
utility commands like, for example, DROP OPERATOR CLASS.
I haven't tried this to see just how much we'd have to dike out, but
my guess is that we could push the ecpg grammar down to something that
would get through stock bison without omitting anything anyone's even
remotely likely to miss.
This is, of course, an ugly hack that we'd want to undo once more
capable versions of bison are readily available. But I think it could
tide us over for a release or two.
Comments?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
