Re: initdb recommendations

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Andrew Dunstan <andrew(dot)dunstan(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-23 06:12:12
Message-ID: 4bfcca1d-220c-850d-a3e2-5f44261331c2@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

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.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Daniel Gustafsson 2019-07-24 08:28:07 Re: Formatting of warning about using ident
Previous Message Jonathan S. Katz 2019-07-22 22:48:11 Re: initdb recommendations

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2019-07-23 06:45:53 Re: Race conditions with TAP test for syncrep
Previous Message David Rowley 2019-07-23 06:11:51 Re: Speed up transaction completion faster after many relations are accessed in a transaction