On Tue, 2009-09-15 at 08:08 -0600, Joshua Tolley wrote: > Perhaps the tuple that caused the violation as well, like UNIQUE index > violations already do? Even if we know what constraint has been tripped, we > might not know what value did it.
Or, even better, include both tuples. With these new constraints the conflicting tuples aren't necessarily equal. Regards, Jeff Davis -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers