Re: Memo on dropping practices - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Memo on dropping practices
Date
Msg-id 1026527892.30427.62.camel@jester
Whole thread Raw
In response to Re: Memo on dropping practices  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Memo on dropping practices
Re: Memo on dropping practices
List pgsql-hackers
>     * Add pg_depend table for dependency recording; use sysrelid, oid,
>       depend_sysrelid, depend_oid, name
>     * Auto-destroy sequence on DROP of table with SERIAL; perhaps a separate
>       SERIAL type
>     * Have SERIAL generate non-colliding sequence names when we have 
>       auto-destruction
>     * Prevent column dropping if column is used by foreign key
>     * Propagate column or table renaming to foreign key constraints
>     * Automatically drop constraints/functions when object is dropped
>     * Make constraints clearer in dump file
>     * Make foreign keys easier to identify
>     * Flush cached query plans when their underlying catalog data changes
> 
> Which of these are done with the patch?

Below is what I listed off as complete when submitting the patch.

'Make constraints clearer in dump file' is questionable.  Foreign keys
are, others not yet, but they need to be.


# Add ALTER TABLE DROP non-CHECK CONSTRAINT
# Allow psql \d to show foreign keys
*  Add pg_depend table for dependency recording; use sysrelid, oid, 
depend_sysrelid, depend_oid, name
# Auto-destroy sequence on DROP of table with SERIAL
# Prevent column dropping if column is used by foreign key
# Automatically drop constraints/functions when object is dropped
# Make constraints clearer in dump file
# Make foreign keys easier to identify



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Memo on dropping practices
Next
From: Bruce Momjian
Date:
Subject: Re: Memo on dropping practices