Re: double vacuum in initdb

On Thu, Dec 11, 2014 at 08:35:43PM -0500, Peter Eisentraut wrote:
> 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.

I have create the attached initdb patch to update this.

> 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.

It is a long-standing TODO item I tried to fix, but couldn't:

    Allow VACUUM FULL and CLUSTER to update the visibility map

        index-only scans : abnormal heap fetches after VACUUM FULL
        http://www.postgresql.org/message-id/20130112191404.255800@gmx.com

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + Everyone has their own god. +