From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Querying dependencies |
Date: | 2023-05-22 18:11:53 |
Message-ID: | 710259.1684779113@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Wells Oliver <wells(dot)oliver(at)gmail(dot)com> writes:
> Sometimes I'll "drop table .." on a replica just to see the list of
> dependencies,.. This is quite dumb. What's the simple query I can run to
> get the same detail without the idiocy?
Not sure about "simple", but here's an example of looking at the
catalog data for this:
regression=# create table mytable(a int primary key, b text unique);
CREATE TABLE
regression=# create table othertable (a int references mytable);
CREATE TABLE
regression=# select pg_describe_object(classid,objid,objsubid), deptype from pg_depend where refclassid = 'pg_class'::regclass and refobjid = 'mytable'::regclass;
pg_describe_object | deptype
--------------------------------------------------+---------
type mytable | i
toast table pg_toast.pg_toast_40635 | i
constraint mytable_pkey on table mytable | a
constraint othertable_a_fkey on table othertable | n
constraint mytable_b_key on table mytable | a
(5 rows)
See https://www.postgresql.org/docs/current/catalog-pg-depend.html
In the general case you'd need to worry about indirect
dependencies, so you'd need to embed this in a recursive
CTE. But tables don't usually have indirect dependencies.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | André Rodrigues | 2023-05-22 18:58:12 | Logical Replication |
Previous Message | Wells Oliver | 2023-05-22 18:01:12 | Querying dependencies |