From: Magnus Hagander <magnus@hagander.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Jonathan S. Katz <jkatz@postgresql.org>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: initdb recommendations
Date: Sat, 6 Apr 2019 11:35:44 +0200
Message-ID: <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com> (raw)
In-Reply-To: <f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com>
References: <bec17f0a-ddb1-8b95-5e69-368d9d0a3390@postgresql.org>
<f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com>
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.
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.
That said, I think it would make sense to *also* have a warning. And in
particular, we should strongly consider backpatching a warning.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/;
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: magnus@hagander.net, peter.eisentraut@2ndquadrant.com, jkatz@postgresql.org, pgsql-docs@lists.postgresql.org
Subject: Re: initdb recommendations
In-Reply-To: <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox