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.

Regards,
	Jeff Davis

Responses

• Re: small exclusion constraints patch at 2010-05-21 19:24:35 from Tom Lane
• Re: small exclusion constraints patch at 2010-07-16 00:46:22 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2010-05-21 19:13:22
	Subject: Re: Specification for Trusted PLs?
Previous:	From: Stephen Frost	Date: 2010-05-21 18:57:23
	Subject: Re: Specification for Trusted PLs?