https://github.com/postgres/postgres
Revision 9a743ffdd6b2fe7a24089fc97d8efc98884e337d authored by Tom Lane on 15 October 2011, 00:24:57 UTC, committed by Tom Lane on 15 October 2011, 00:24:57 UTC
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).
1 parent 7a0c584
Raw File
Tip revision: 9a743ffdd6b2fe7a24089fc97d8efc98884e337d authored by Tom Lane on 15 October 2011, 00:24:57 UTC
Fix bugs in information_schema.referential_constraints view.
Tip revision: 9a743ff
README.git
(This file does not appear in release tarballs.)

In a release or snapshot tarball of PostgreSQL, documentation files named
INSTALL and HISTORY will appear in this directory.  However, these files are
not stored in git and so will not be present if you are using a git checkout.
If you are using git, you can view the most recent install instructions at:
	http://developer.postgresql.org/docs/postgres/installation.html
and the current release notes at:
	http://developer.postgresql.org/docs/postgres/release.html

Users compiling from git will also need compatible versions of Bison, Flex,
and Perl, as discussed in the install documentation.  These programs are not
needed when using a tarball, since the files they are needed to build are
already present in the tarball.  (On Windows, however, you need Perl anyway.)
back to top