Re: Why do pg_upgrade's test use the serial schedule?

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <bruce(at)momjian(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Subject: Re: Why do pg_upgrade's test use the serial schedule?
Date: 2018-11-05 22:11:42
Message-ID: 20181105221142.al6vsfuat3dtzobx@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-11-05 17:08:12 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-11-05 22:25:09 Re: BUG #15212: Default values in partition tables don't work as expected and allow NOT NULL violation
Previous Message Tom Lane 2018-11-05 22:08:12 Re: Why do pg_upgrade's test use the serial schedule?