Re: double vacuum in initdb

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: double vacuum in initdb
Date: 2014-12-12 01:35:43
Message-ID: 548A466F.4070202@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-12-12 01:37:34 Re: [Bug] Inconsistent result for inheritance and FOR UPDATE.
Previous Message Michael Paquier 2014-12-12 01:31:33 Re: Proposal : REINDEX SCHEMA