MIME-Version: 1.0
References: <bec17f0a-ddb1-8b95-5e69-368d9d0a3390@postgresql.org>
 <f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com>
In-Reply-To: <f27d3170-76cf-4afb-1e1a-b1059295ec8d@2ndquadrant.com>
From: Magnus Hagander <magnus@hagander.net>
Date: Sat, 6 Apr 2019 11:35:44 +0200
Message-ID: 
 <CABUevExMizVYea9zaHBte66u9KipEgfwcsaE9spfqK9iYRST_g@mail.gmail.com>
Subject: Re: initdb recommendations
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>,
 Pg Docs <pgsql-docs@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="0000000000008d36340585d95415"
Precedence: bulk

--0000000000008d36340585d95415
Content-Type: text/plain; charset="UTF-8"

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

--0000000000008d36340585d95415
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Apr 5, 2019 at 10:58 PM Peter=
 Eisentraut &lt;<a href=3D"mailto:peter.eisentraut@2ndquadrant.com">peter.e=
isentraut@2ndquadrant.com</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">On 2019-04-05 18:11, Jonathan S. Katz wrote:<br>
&gt; (There could be an additional discussion about whether or not we want =
to<br>
&gt; change the default behavior for initdb, but I would suggest that a saf=
e<br>
&gt; starting point would be to ensure we call this out)<br>
<br>
I think we should just change the defaults.=C2=A0 There is a risk of warnin=
g<br>
fatigue.=C2=A0 initdb does warn about this, so anyone who cared could have<=
br>
gotten the information.<br></blockquote><div><br></div><div>I&#39;ve been s=
uggesting that for years, so definite strong=C2=A0+1 for doing that.</div><=
div><br></div><div>If it&#39;s something that annoys backend developers who=
 initdb very often, I suggest we add an environment variable to override it=
. But I&#39;m not sure that&#39;s really necessary -- creating a shell alia=
s or similar is easy to do, and most have probably already done so for othe=
r reasons.</div></div><div><br></div><div>That said, I think it would make =
sense to *also* have a warning. And in particular, we should strongly consi=
der backpatching a warning.</div><div><br></div>-- <br><div dir=3D"ltr" cla=
ss=3D"gmail_signature"><div dir=3D"ltr"><div>=C2=A0Magnus Hagander<br>=C2=
=A0Me: <a href=3D"http://www.hagander.net/" target=3D"_blank">https://www.h=
agander.net/</a><br>=C2=A0Work: <a href=3D"http://www.redpill-linpro.com/" =
target=3D"_blank">https://www.redpill-linpro.com/</a></div></div></div></di=
v>

--0000000000008d36340585d95415--