Postgres Pro
Downloads
Home   >   mailing lists

Re: Why do pg_upgrade's test use the serial schedule? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Why do pg_upgrade's test use the serial schedule?
Date
Msg-id 20181105221142.al6vsfuat3dtzobx@alap3.anarazel.de
Whole thread Raw
In response to Re: Why do pg_upgrade's test use the serial schedule?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Why do pg_upgrade's test use the serial schedule?
List pgsql-hackers
Tree view 
On 2018-11-05 17:08:12 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > On 2018-11-05 16:32:20 -0500, Tom Lane wrote:
> >> It's injected via the TEMP_CONFIG env variable.
> 
> > Ah, thanks.  Is there any good reason to not instead have it in the
> > script?
> 
> Why that script in particular?

Because just about everything else taking substantial time already
disables it. pg_regress forks off a postmaster with -F, the tap tests do
so for large portions via fsync=off in the config (c.f. PostgresNode.pm).

Greetings,

Andres Freund

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why do pg_upgrade's test use the serial schedule?
Next
From: Alvaro Herrera
Date:
Subject: Re: BUG #15212: Default values in partition tables don't work asexpected and allow NOT NULL violation