Date: Sat, 6 Apr 2019 11:08:39 -0700
From: Noah Misch <noah@leadboat.com>
To: Magnus Hagander <magnus@hagander.net>
Cc: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
	"Jonathan S. Katz" <jkatz@postgresql.org>,
	Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: initdb recommendations
Message-ID: <20190406180839.GA1921989@rfd.leadboat.com>
References: <bec17f0a-ddb1-8b95-5e69-368d9d0a3390@postgresql.org>
 <f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com>
 <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: 
 <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Precedence: bulk

On Sat, Apr 06, 2019 at 11:35:44AM +0200, Magnus Hagander wrote:
> On Fri, Apr 5, 2019 at 10:58 PM Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote:
> > On 2019-04-05 18:11, Jonathan S. Katz wrote:
> > > (There could be an additional discussion about whether or not we want to
> > > change the default behavior for initdb, but I would suggest that a safe
> > > starting point would be to ensure we call this out)
> >
> > I think we should just change the defaults.  There is a risk of warning
> > fatigue.  initdb does warn about this, so anyone who cared could have
> > gotten the information.
> >
> 
> I've been suggesting that for years, so definite strong +1 for doing that.

+1

> If it's something that annoys backend developers who initdb very often, I
> suggest we add an environment variable to override it. But I'm not sure
> that's really necessary -- creating a shell alias or similar is easy to do,
> and most have probably already done so for other reasons.

I, for one, do most initdb runs via a script and wouldn't use such an
environment variable.