>>> "Wayne Conrad" <wcon...@yagni.com> wrote: > "VACUUM FULL ANALYZE VERBOSE" on a "deadlocks" > "VACUUM VERBOSE ANALYZE" (without the "FULL") does not You do realize that FULL should not be part of normal maintenance, right? It is sometimes useful to recover from table bloat when normal maintenance fails. Although it is almost always much slower than CLUSTER, it has the advantage of not requiring disk space for a second copy of the table, but it requires a REINDEX afterward to correct the index bloat it causes. If you are doing a good job of normal maintenance, you never, ever should be running VACUUM FULL. None of the above means you haven't found a problem worth looking at -- I'm not trying to comment on that; but unless you are in the middle of recovery from abnormal bloat, you may be able to dodge the problem by correcting your maintenance practices. -Kevin
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
