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