| From: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: initdb recommendations |
| Date: | 2019-07-24 14:00:34 |
| Message-ID: | 654cbc96-0b32-6d00-09a8-5caf5d051103@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Awad Mackie | 2019-07-24 17:22:35 | Re: REFRESH MATERIALIZED VIEW CONCURRENTLY interaction with ORDER BY |
| Previous Message | Andrew Dunstan | 2019-07-24 13:55:05 | Re: initdb recommendations |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2019-07-24 14:38:47 | Re: Compile from source using latest Microsoft Windows SDK |
| Previous Message | Alexander Korotkov | 2019-07-24 13:59:11 | Re: Psql patch to show access methods info |