On Sun, Mar 12, 2017 at 11:14 PM, Michael Paquier
<michael.paqu...@gmail.com> wrote:
> On Mon, Mar 13, 2017 at 9:15 AM, Robert Haas <robertmh...@gmail.com> wrote:
>> On Fri, Mar 10, 2017 at 5:43 PM, Michael Paquier
>> <michael.paqu...@gmail.com> wrote:
>>> On Sat, Mar 11, 2017 at 2:53 AM, Jeff Janes <jeff.ja...@gmail.com> wrote:
>>>> Should the \password tool in psql inspect password_encryption and act on it
>>>> being 'scram'?
>>> Not sure if it is wise to change the default fot this release.
>> Seems like an odd way to phrase it.  Aren't we talking about making a
>> feature that worked in previous releases continue to work?
> Considering how fresh scram is, it seems clear to me that we do not
> want to just switch the default values of password_encryption, the
> default behaviors of PQencryptPassword() and \password only to scram,
> but have something else. Actually if we change nothing for default
> deployments of Postgres using md5, PQencryptPassword() and \password
> would still work properly.

I'm not talking about changing the default, just having it be possible
to use \password with the new system as it was with the old, whatever
exactly we think that means.

Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to