Jeff Davis <pgsql@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