Skip site navigation (1) Skip section navigation (2)

pg_depend take 2

From: Rod Taylor <rbt(at)zort(dot)ca>
To: pgsql-patches(at)postgresql(dot)org
Subject: pg_depend take 2
Date: 2002-04-21 02:03:56
Message-ID: 1019354637.8075.13.camel@knight.zort.ca (view raw or flat)
Thread:
Lists: pgsql-patches
Major changes since last revision:

initdb changes to account for table structure and new PIN elements for
genbki.sh.  Enables really easy pinning of data in a table you know the
ID of.

Most objects enforced RESTRICT / CASCADE options.

Still needs code to track foreign keys between tables (right now it
catches the triggers -- but not the relation.  See 'Foreign keys and
indexes' on hackers.

Serials sequences are dropped with the cascade.

'drop' regression test rewritten to test restrict / cascade of various
stuff.  It may be missing a few things, but implicit cascades are
defined elsewhere (indexes, triggers, etc.)

Thoughts:
Do system objects depend on users?  DROP USER ... CASCADE (drop all
tables, triggers, etc. that the user owns).

Will schemas auto-cascade to everything within them using the normal
DROP stuff or should all objects in a schema depend on the schema
implicitly?  Allows RESTRICT / CASCADE of a schema fairly quickly.
(Tom?)



Attachment: pg_depend.h
Description: text/x-c-header (2.8 KB)
Attachment: pg_depend.c
Description: text/x-c (17.7 KB)
Attachment: drop.out
Description: text/plain (5.0 KB)
Attachment: TODO.depend
Description: text/plain (2.1 KB)
Attachment: depend.patch
Description: text/plain (115.0 KB)

pgsql-patches by date

Next:From: Gavin SherryDate: 2002-04-21 17:39:46
Subject: Re: [HACKERS] WITH DELIMITERS in COPY
Previous:From: Joe ConwayDate: 2002-04-20 06:01:19
Subject: doc patch for ALTER TRIGGER

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group