Awhile back Csaba Nagy <[EMAIL PROTECTED]> wrote: > Making cluster MVCC-safe will kill my back-door of clustering a hot > table while I run a full DB backup.
Are we agreed that the TRUNCATE-based workaround shown here http://archives.postgresql.org/pgsql-hackers/2007-03/msg00606.php is an adequate response to this objection? (This assumes of course that TRUNCATE will never become MVCC-safe, but I think that's a reasonable thing to assume. I notice we don't document TRUNCATE as unsafe ... will go fix that.) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
