| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: scram and \password |
| Date: | 2017-03-17 13:31:30 |
| Message-ID: | CA+TgmoZ0MZCL8A90+9rvLjrgtnq1ZJSquQ+-6EVf5mhT6e4m4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 17, 2017 at 8:32 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> It would make sense to have \password obey password_encryption GUC. Then
> \password and ALTER USER would do the same thing, which would be less
> surprising. Although it's also a bit weird for a GUC to affect client-side
> behavior, so perhaps better to just document that \password will create a
> SCRAM verifier, unless you explicitly tell it to create an MD5 hash, and add
> a 'method' parameter to it.
Either of those would be fine with me, but I think we should do one of them.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-17 13:33:24 | Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless) |
| Previous Message | Ashutosh Bapat | 2017-03-17 13:15:45 | Re: Partition-wise join for join between (declaratively) partitioned tables |