Re: double vacuum in initdb

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: double vacuum in initdb
Date: 2015-03-31 15:51:54
Message-ID: 20150331155154.GF4466@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 20, 2015 at 10:59:41PM -0400, Bruce Momjian wrote:
> 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.

Patch applied.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ Everyone has their own god. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-03-31 16:10:48 Re: [COMMITTERS] pgsql: Centralize definition of integer limits.
Previous Message Bruce Momjian 2015-03-31 15:46:53 Re: Change of pg_ctl's default shutdown method