Re: double vacuum in initdb - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: double vacuum in initdb
Date
Msg-id 548A466F.4070202@gmx.net
Whole thread Raw
In response to Re: double vacuum in initdb  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: double vacuum in initdb  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 12/11/14 11:44 AM, Kevin Grittner wrote:
> We want to finish with VACUUM FREEZE without the FULL, unless we
> don't care about missing visibility maps and free space maps.

Why would we care, and if we do, why does VACUUM FULL remove them?

You can also run plain VACUUM after FULL to put the maps back.

But the documentation is apparently missing details about this.




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Proposal : REINDEX SCHEMA
Next
From: Tom Lane
Date:
Subject: Re: [Bug] Inconsistent result for inheritance and FOR UPDATE.