From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Alex Pilosov <alex(at)pilosoft(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_depend |
Date: | 2001-07-17 16:46:35 |
Message-ID: | 200107171646.f6HGkZM13463@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> When a table is dropped, you scan all of these objects (their system
> catalogs) for matches against the table and either do a cascade or
> restrict. This is not new, we already do this for indexes and
> descriptions, for instance.
I was thinking we could centralize all that checking in pg_depend.
However, we could decide just to do the areas where system tables don't
work, like foreign keys and sequences. But when I find an oid depends
on me, do I start scanning tables looking to see if is a sequence or a
foreign key?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-07-17 17:21:34 | Re: SIGCHLD handler in Postgres C function. |
Previous Message | Peter Eisentraut | 2001-07-17 16:44:25 | Re: pg_depend |