I think your two alternatives are to either make sure no constraint names are duplicated, or add a unique key for conname to pg_constraint. I didn;t know constraint name was a SQL requirement. I can see how the information_schema would be designed to assume they were unique if it was.
-- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
