On Wed, Dec 15, 2010 at 10:50 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > On Wed, 2010-12-15 at 12:17 +0100, Csaba Nagy wrote: > >> But one problem would be when the replaced table is the _parent_ for a >> foreign key relationship. I don't think you can have that constraint >> pre-verified on the replacement table and simply replacing the content >> could leave the child relations with orphans. > > Good point. > > The only sensible way to handle this is by putting the FK checks into > check pending state (as discussed on a different thread). > > We would probably need to disallow FKs with DELETE or UPDATE CASCADE > since it would be difficult to execute those.
I'm still wondering if TRUNCATE CONCURRENTLY would be a more elegant solution. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
