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

On 2018-11-05 16:32:20 -0500, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2018-11-05 16:10:28 -0500, Tom Lane wrote:
> >> Andres Freund <andres(at)anarazel(dot)de> writes:
> >>> ISTM we also should disable fsyncs for the postmaster instances. Wins
> >>> another ~5s on my laptop, and I suspect it makes a larger difference on
> >>> some of the buildfarm animals.
>
> >> Buildfarm did that long ago.
>
> > I don't think it did for pg_upgrade's test.sh?
>
> It's injected via the TEMP_CONFIG env variable.

Ah, thanks. Is there any good reason to not instead have it in the
script? Doesn't strike me as great that it slows down normal regression
runs during development? Injecting TEMP_CONFIG w/ fsync=off globally
for those (rather than in a single test wrapper), could counteract
explicit tests where fsync is wanted - beside the fact that one has to
do so manually. Normal regression tests have long done so.

Greetings,

Andres Freund