From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Beth Gatewood" <beth(at)vizxlabs(dot)com> |
Cc: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: query system tables to find columns unique constraint is constraining? |
Date: | 2002-05-28 19:10:33 |
Message-ID: | 15686.1022613033@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"Beth Gatewood" <beth(at)vizxlabs(dot)com> writes:
> I have been fiddling around trying to figure out which columns some unique
> constraints are constraining by querying the system tables.....with zero
> luck.
Look at the pg_index row for the index that's implementing the
constraint.
Rather than messing with the pg_index entry directly, you might want to
use pg_get_indexdef(), which is a helper function for pg_dump:
regression=# create table foo (f1 int, constraint foo_f1 unique (f1));
NOTICE: CREATE TABLE / UNIQUE will create implicit index 'foo_f1' for table 'foo'
CREATE TABLE
regression=# select pg_get_indexdef(oid) from pg_class where relname = 'foo_f1';
pg_get_indexdef
----------------------------------------------------
CREATE UNIQUE INDEX foo_f1 ON foo USING btree (f1)
(1 row)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2002-05-28 21:12:28 | Re: query system tables to find columns unique constraint is constraining? |
Previous Message | Beth Gatewood | 2002-05-28 18:47:02 | query system tables to find columns unique constraint is constraining? |