From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vik Fearing <vik(at)postgresfriends(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: password_encryption default |
Date: | 2020-05-27 13:13:35 |
Message-ID: | 20200527131335.GH103662@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 27, 2020 at 02:56:34PM +0200, Magnus Hagander wrote:
> Seems like the better choice yeah. Since we're changing the default anyway,
> maybe now is the time to do that? Or if not, maybe have it log an explicit
> deprecation warning when it loads a config with it?
Not sure that's worth it here, so I would just remove the whole. It
would be confusing to keep the past values and have them map to
something we think is not an appropriate default.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2020-05-27 13:21:24 | Re: Getting ERROR with FOR UPDATE/SHARE for partitioned table. |
Previous Message | Magnus Hagander | 2020-05-27 12:56:34 | Re: password_encryption default |