Re: initdb recommendations
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>,
Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2019-07-24T14:00:34Z
Lists: pgsql-hackers, pgsql-docs
On 7/23/19 2:12 AM, Peter Eisentraut wrote: > On 2019-07-22 21:16, Andrew Dunstan wrote: >> Modulo this issue, experimentation shows that adding '-A trust' to the >> line in run_build.pl where initdb is called fixes the issue. If we're >> going to rely on a buildfarm client fix that one seems simplest. > Yes, that is the right fix. It's what the in-tree test drivers > (pg_regress, PostgresNode.pm) do. > I have done that, I will put out a new release probably right after the CF closes. I think we also need to change vcregress.pl to use trust explicitly for upgrade checks, just like the Unix upgrade test script does. That should help to future-proof us a bit. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
initdb: Change authentication defaults
- 09f08930f0f6 13.0 landed