On Tue, Dec 14, 2010 at 1:54 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > BEGIN; > TRUNCATE TABLE; > ... load new data ... > COMMIT;
Because then you have to take an AccessExclusiveLock on the target table, of course. If we had some kind of TRUNCATE CONCURRENTLY, I think that'd address a large portion of the use case for the proposed feature. -- 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
