Prev: [HACKERS] buildfarm owners, please add REL9_0_STABLE to your list of builds
Next: [HACKERS] buildfarm housekeeping / planning
From: Tom Lane on 15 Jul 2010 20:46
Jeff Davis <pgsql(a)j-davis.com> writes:
> Currently, the check for exclusion constraints performs a sanity check
> that's slightly too strict -- it assumes that a tuple will conflict with
> itself. That is not always the case: the operator might be "<>", in
> which case it's perfectly valid for the search for conflicts to not find
> itself.

> This patch simply removes that sanity check, and leaves a comment in
> place.

Applied (for 9.1 only).

regards, tom lane

--
Sent via pgsql-hackers mailing list (pgsql-hackers(a)postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

 | 
Pages: 1
Prev: [HACKERS] buildfarm owners, please add REL9_0_STABLE to your list of builds
Next: [HACKERS] buildfarm housekeeping / planning