Re: initdb recommendations - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: initdb recommendations
Date
Msg-id 654cbc96-0b32-6d00-09a8-5caf5d051103@2ndQuadrant.com
Whole thread Raw
In response to Re: initdb recommendations  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: initdb recommendations  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: initdb recommendations  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-hackers
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




pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Psql patch to show access methods info
Next
From: Andrew Dunstan
Date:
Subject: Re: Compile from source using latest Microsoft Windows SDK