New system catalog idea
While we're on the subject of new system catalogs, how about a many to many
catalog like this:
pg_depend (oid obj, oid dep)
That maps the oid of a system object (such as a constraint, index, function,
trigger, anything) to all other system objects that are dependent upon it.
Although it may take a bit of work to implement, it will trivialise
supporting CASCADE/RESTRICT on DROP.
Chris
I think this is a good idea, and something to add to the TODO list. We
are hitting too many of these gotchas.
* Add pg_depend table to track object dependencies
[ Charset ISO-8859-1 unsupported, converting... ]
While we're on the subject of new system catalogs, how about a many to many
catalog like this:pg_depend (oid obj, oid dep)
That maps the oid of a system object (such as a constraint, index, function,
trigger, anything) to all other system objects that are dependent upon it.
Although it may take a bit of work to implement, it will trivialise
supporting CASCADE/RESTRICT on DROP.Chris
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026