| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "steven(dot)winfield(at)cantabcapital(dot)com" <steven(dot)winfield(at)cantabcapital(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: CREATE/ALTER ROLE with NULL password |
| Date: | 2018-11-22 07:58:06 |
| Message-ID: | 20181122075806.GK3369@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, Nov 21, 2018 at 11:58:25PM -0700, David G. Johnston wrote:
> Should tweak the paragraph to point out this exception as well.
>
> The ENCRYPTED keyword has no effect, but is accepted for backwards
> compatibility[, except in the PASSWORD NULL form.]
The docs list the following with the patch as supported grammar:
[ ENCRYPTED ] PASSWORD 'password' | PASSWORD NULL
And it seems to me that '|' has priority over '[]', so ENCRYPTED does
not apply to PASSWORD NULL if phrased this way.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2018-11-22 16:54:07 | Re: CREATE/ALTER ROLE with NULL password |
| Previous Message | David G. Johnston | 2018-11-22 06:58:25 | Re: CREATE/ALTER ROLE with NULL password |