Re: Draft release notes for 9.3.2 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Draft release notes for 9.3.2
Date
Msg-id 20131202192400.GD15336@awork2.anarazel.de
Whole thread Raw
In response to Re: Draft release notes for 9.3.2  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Draft release notes for 9.3.2
Next
From: Tom Lane
Date:
Subject: Re: Draft release notes for 9.3.2