]> git.ipfire.org Git - thirdparty/postgresql.git/commit
Fix bugs in information_schema.referential_constraints view.
authorTom Lane <tgl@sss.pgh.pa.us>
Sat, 15 Oct 2011 00:24:42 +0000 (20:24 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Sat, 15 Oct 2011 00:24:42 +0000 (20:24 -0400)
commit6d363e0d2f30461a8f8b00c953828fb7135cd9e5
tree0c6044f1f1f3cdbd3e0f92cb6c6a8303f29f82a0
parent77ea00406998d0f58e71a433f6cfe40fda2368b9
Fix bugs in information_schema.referential_constraints view.

This view was being insufficiently careful about matching the FK constraint
to the depended-on primary or unique key constraint.  That could result in
failure to show an FK constraint at all, or showing it multiple times, or
claiming that it depended on a different constraint than the one it really
does.  Fix by joining via pg_depend to ensure that we find only the correct
dependency.

Back-patch, but don't bump catversion because we can't force initdb in back
branches.  The next minor-version release notes should explain that if you
need to fix this in an existing installation, you can drop the
information_schema schema then re-create it by sourcing
$SHAREDIR/information_schema.sql in each database (as a superuser of
course).
src/backend/catalog/information_schema.sql