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


Mon, 21 May 2001 09:58:37 +0800
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
New system catalog idea

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

Mon, 21 May 2001 21:35:11 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: New system catalog idea