On 2013-12-02 10:51:28 -0800, Josh Berkus wrote: > Tom, > > "The issue can be ameliorated by, after upgrading, vacuuming all tables > in all databases while having vacuum_freeze_table_age set to zero. " > > Why not say: > > "This issue can be ameliorated by, after upgrading, running a > database-wide VACUUM FREEZE." > > Or is there a difference in this case? If so, what?
vacuum_freeze_table age causes a full table scan, but doesn't freeze rows younger than vacuum_freeze_min_age. I.e. it finishes much faster. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
