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.
information_schema.sql (r1.37 -> r1.38)
pgsql-committers by date
|Next:||From: Tom Lane||Date: 2006-11-10 20:52:18|
|Subject: pgsql: Emphasize that immutable and stable functions are not allowed to |
|Previous:||From: User Dpage||Date: 2006-11-10 17:06:09|
|Subject: pginstaller - pginst: Update for PostGIS 1.1.6|