From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Noah Misch <noah(at)leadboat(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org> |
Subject: | Re: initdb recommendations |
Date: | 2019-06-18 20:33:38 |
Message-ID: | fcd8848c-618c-23d1-2b39-77b13cb2d0a1@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-hackers |
On 2019-05-23 18:54, Peter Eisentraut wrote:
> To recap, the idea here was to change the default authentication methods
> that initdb sets up, in place of "trust".
>
> I think the ideal scenario would be to use "peer" for local and some
> appropriate password method (being discussed elsewhere) for host.
Patch for that attached.
> Looking through the buildfarm, I gather that the only platforms that
> don't support peer are Windows, AIX, and HP-UX.
Note that with this change, running initdb without arguments will now
error on those platforms: You need to supply either a password or select
a different default authentication method.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v1-0001-initdb-Change-authentication-defaults.patch | text/plain | 7.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | PG Doc comments form | 2019-06-19 16:23:08 | postgresql.conf |
Previous Message | Michael Paquier | 2019-06-17 02:10:29 | Re: SPITupleTable members missing in docs |
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2019-06-18 20:59:20 | Choosing values for multivariate MCV lists |
Previous Message | Li, Zheng | 2019-06-18 20:22:30 | Re: NOT IN subquery optimization |