Re: operator exclusion constraints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: operator exclusion constraints
Date: 2009-11-07 02:54:40
Message-ID: 13765.1257562480@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> This is a pretty good short explanation of how to deal with shift/reduce
> problems in bison. With your permission I'm going to copy it to the Wiki

If you like, but I think the part about figuring out which production
is the problem seemed to be at least as important for Jeff ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-07 02:57:13 Re: Specific names for plpgsql variable-resolution control options?
Previous Message Andrew Dunstan 2009-11-07 02:53:20 Re: plperl and inline functions -- first draft