Skip site navigation (1) Skip section navigation (2)

pgsql: Fix errors in key_column_usage.position_in_unique_constraint

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix errors in key_column_usage.position_in_unique_constraint
Date: 2006-11-10 18:10:10
Message-ID: 20061110181010.282469FB2C4@postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix errors in key_column_usage.position_in_unique_constraint column recently
added to information_schema (per a SQL2003 addition).  The original coding
failed if a referenced column participated in more than one pg_constraint
entry.  Also, it did not work if an FK relied directly on a unique index
without any constraint syntactic sugar --- this case is outside the SQL spec,
but PG has always supported it, so it's reasonable for our information_schema
to handle it too.  Per bug#2750 from Stephen Haberman.

Although this patch changes the initial catalog contents, I didn't force
initdb.  Any beta3 testers who need the fix can install it via CREATE OR
REPLACE VIEW, so forcing them to initdb seems an unnecessary imposition.

Modified Files:
--------------
    pgsql/src/backend/catalog:
        information_schema.sql (r1.37 -> r1.38)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/catalog/information_schema.sql.diff?r1=1.37&r2=1.38)

pgsql-committers by date

Next:From: Tom LaneDate: 2006-11-10 20:52:18
Subject: pgsql: Emphasize that immutable and stable functions are not allowed to
Previous:From: User DpageDate: 2006-11-10 17:06:09
Subject: pginstaller - pginst: Update for PostGIS 1.1.6

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group