Tom Lane 7bddca3450 Fix up foreign-key mechanism so that there is a sound semantic basis for the ... equality checks it applies, instead of a random dependence on whatever operators might be named "=". The equality operators will now be selected from the opfamily of the unique index that the FK constraint depends on to enforce uniqueness of the referenced columns; therefore they are certain to be consistent with that index's notion of equality. Among other things this should fix the problem noted awhile back that pg_dump may fail for foreign-key constraints on user-defined types when the required operators aren't in the search path. This also means that the former warning condition about "foreign key constraint will require costly sequential scans" is gone: if the comparison condition isn't indexable then we'll reject the constraint entirely. All per past discussions. Along the way, make the RI triggers look into pg_constraint for their information, instead of using pg_trigger.tgargs; and get rid of the always error-prone fixed-size string buffers in ri_triggers.c in favor of building up the RI queries in StringInfo buffers. initdb forced due to columns added to pg_constraint and pg_trigger.		2007-02-14 01:58:58 +00:00
..
dest.c	Update CVS HEAD for 2007 copyright. Back branches are typically not	2007-01-05 22:20:05 +00:00
fastpath.c	Update CVS HEAD for 2007 copyright. Back branches are typically not	2007-01-05 22:20:05 +00:00
Makefile	Remove remains of old depend target.	2007-01-20 17:16:17 +00:00
postgres.c	StrNCpy -> strlcpy (not complete)	2007-02-10 14:58:55 +00:00
pquery.c	Update CVS HEAD for 2007 copyright. Back branches are typically not	2007-01-05 22:20:05 +00:00
utility.c	Fix up foreign-key mechanism so that there is a sound semantic basis for the	2007-02-14 01:58:58 +00:00