Kevin Grittner wrote: > Kevin Kempter <kevink@xxxxxxxxxxxxxxxxxxx> wrote: > > 2) can I safely kill the vacuum full and do a dump, drop table, > > restore instead? > > Killing a VACUUM FULL can leave the table or its indexes more bloated > than when you started, but it should have no other negative impact. I > have generally had to kill my attempts to VACUUM FULL and resort to > other techniques to deal with extreme bloat. Note that cancelling a VACUUM FULL is known to cause a database restart (a.k.a. PANIC) if the circumstances are right, viz. that the initial transaction committed. This is an unfixable bug (short of rewriting vacuum full from scratch) and has been reported in the wild several times. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
