From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
cc: Andres Freund <andres@anarazel.de>, Noah Misch <noah@leadboat.com>,
        David Rowley <dgrowleyml@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Intermittent buildfarm failures on wrasse
In-reply-to: 
 <CAH2-WznQ2j3n9QwfJ5Cp6RAPfbYCkh-Bgj2Vyk6Qh_HwFULRYw@mail.gmail.com>
References: <1364997.1649893086@sss.pgh.pa.us>
 <CAH2-WzkUGqFNXhnFRbVG4xfTo3WpapcdRaH4hQSTrNvDgYvYoQ@mail.gmail.com>
 <1365924.1649893883@sss.pgh.pa.us>
 <CAH2-Wzn2Obp90oyZa5HN26rzG8ozzHM3dgkpLcsVzxTR+jK5NQ@mail.gmail.com>
 <1374062.1649896550@sss.pgh.pa.us>
 <20220414010505.s7z24jxrfsjbzz7l@alap3.anarazel.de>
 <1401379.1649899392@sss.pgh.pa.us>
 <20220414015112.yhruzx3dbjnz4pji@alap3.anarazel.de>
 <20220414025122.GA808845@rfd.leadboat.com> <1486022.1649952083@sss.pgh.pa.us>
 <20220414161850.ibqkevxcv6a7vdxg@alap3.anarazel.de>
 <1521388.1649953580@sss.pgh.pa.us> <1547912.1649971995@sss.pgh.pa.us>
 <CAH2-Wz=DHY2LV7=2aVd=qz6AbQhFK7KJRNL5ZwgB7dyno_gzdg@mail.gmail.com>
 <1553951.1649975018@sss.pgh.pa.us>
 <CAH2-WzngTjUk_65ESmrMf40WTqasrmWG0gpwnvcN+mXsoXT7qQ@mail.gmail.com>
 <CAH2-WznXXkkfE_y9ieaHkEQj31HeMAqJBtJPmDY+EpyVg1QywQ@mail.gmail.com>
 <1570894.1649986347@sss.pgh.pa.us>
 <CAH2-WznQ2j3n9QwfJ5Cp6RAPfbYCkh-Bgj2Vyk6Qh_HwFULRYw@mail.gmail.com>
Comments: In-reply-to Peter Geoghegan <pg@bowt.ie>
	message dated "Thu, 14 Apr 2022 18:49:48 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1572436.1649987614.1@sss.pgh.pa.us>
Date: Thu, 14 Apr 2022 21:53:34 -0400
Message-ID: <1572437.1649987614@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1572437.1649987614%40sss.pgh.pa.us>
Precedence: bulk

Peter Geoghegan <pg@bowt.ie> writes:
> Anyway, I suppose it's possible that problems reappeared here due to
> some other patch. Something else could have broken Andres' earlier
> band aid solution (which was to set synchronous_commit=on in
> test_setup).

That band-aid only addressed the situation of someone having turned
off synchronous_commit in the first place; which is not the case
on wrasse or most/all other buildfarm animals.  Whatever we're
dealing with here is something independent of that.

> Is there any patch that could plausibly have had that effect, whose
> commit fits with our timeline for the problems seen on wrasse?

I already enumerated my suspects, back at the top of this thread.

			regards, tom lane