Re: operator exclusion constraints
Jeff Davis <pgsql@j-davis.com>
From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Peter Eisentraut <peter_e@gmx.net>, Simon Riggs <simon@2ndquadrant.com>, pgsql-hackers@postgresql.org
Date: 2009-11-07T18:46:33Z
Lists: pgsql-hackers
Attachments
- operator-exclusion-constraints-20091107.context.patch (text/x-patch) patch
- operator-exclusion-constraints-20091107.patch.gz (application/x-gzip) patch
On Fri, 2009-11-06 at 21:20 -0500, Tom Lane wrote: > > bison -v doesn't show anything useful beyond saying that there is one > > shift/reduce conflict. The gram.output is 10MB, which doesn't help me > > much (I'm still trying to make sense of it). > > Well, you need to learn a bit more about bison I think. Yes, I do. Thank you very much for the detailed explanation; it was very informative. I have made the suggested changes, and now it works easily with EXCLUSION, EXCLUDING, EXCLUSIVE, or EXCLUDE. I have also merged with the latest changes, and I did another cleanup pass on the patch. Regards, Jeff Davis