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