From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
cc: Amit Kapila <amit.kapila16@gmail.com>,
        Magnus Hagander <magnus@hagander.net>,
        Andrew Dunstan <andrew.dunstan@2ndquadrant.com>,
        Mark Dilger <hornschnorter@gmail.com>,
        PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Windows buildfarm members vs. new async-notify isolation test
In-reply-to: 
 <CA+hUKGJTiF8rWv8-fPa4dv7fORd2GhuvHKwUA2i1NoVU9nG+GA@mail.gmail.com>
References: <32745.1575303812@sss.pgh.pa.us>
 <7221b3b4-fc7f-404d-5cf6-830d3aa6800d@2ndQuadrant.com>
 <362bca0b-1c1c-c760-ab19-b5d9a14c69ea@gmail.com>
 <13003.1575391248@sss.pgh.pa.us>
 <CAA4eK1+qevZ=sB1nW05_gkiHLWjUU0psNPiutFnQi=+aCztLXA@mail.gmail.com>
 <25746.1575436347@sss.pgh.pa.us>
 <CAA8=A78X-0vVd5tk7r=Z7yEWW5Vy1=46q7wjZaOa8Xaed5FooQ@mail.gmail.com>
 <CAA4eK1+HOFzs=-MHDz6ef936KuuHJBxZbHEi7xt9TBqgHNO9GQ@mail.gmail.com>
 <e1eb7182-a487-42f1-e113-4e5758e8ceef@2ndQuadrant.com>
 <20102.1575675105@sss.pgh.pa.us>
 <CAA4eK1LRwxr51JuXsgpmCA+-uswCHiGvhZ88jPz8VeJxfyv65g@mail.gmail.com>
 <30330.1575739251@sss.pgh.pa.us> <4412.1575748586@sss.pgh.pa.us>
 <9110.1575824266@sss.pgh.pa.us>
 <CAA4eK1Ko-jYO-6FtirWSixd63D_oLyT1KL5srnjXEKMg5QoiNA@mail.gmail.com>
 <7254.1575993433@sss.pgh.pa.us>
 <CAA4eK1LH0HoFXbjgE6Htf9rkGx58QN+=_O2ZNw9fHvv_9+-JgQ@mail.gmail.com>
 <2985.1576095051@sss.pgh.pa.us>
 <CA+hUKGJTiF8rWv8-fPa4dv7fORd2GhuvHKwUA2i1NoVU9nG+GA@mail.gmail.com>
Comments: In-reply-to Thomas Munro <thomas.munro@gmail.com>
	message dated "Sun, 30 Aug 2020 14:52:57 +1200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3757910.1598757705.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 29 Aug 2020 23:21:45 -0400
Message-ID: <3757911.1598757705@sss.pgh.pa.us>
Precedence: bulk

Thomas Munro <thomas.munro@gmail.com> writes:
> I made a thing to watch out for low probability BF failures and it
> told me that a similar failure in async-notify might have reappeared
> on brolga:

>  https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=3Dbrolga&dt=3D2=
020-07-15%2008:30:11
> | REL_10_STABLE
> [ etc ]

Hm, interesting.  None of these examples show an actual *failure* to
receive a notification, unlike the example that began this thread.
So it seems unlikely that back-patching 16114f2ea would help.  What
we are seeing here, instead, is delayed timing of notify receipt(s).
I suspect that this is a variant of the issue described over here:

https://www.postgresql.org/message-id/flat/2527507.1598237598%40sss.pgh.pa=
.us

I didn't have a great idea about how to fix it reliably in
insert-conflict-specconflict, and I lack one here too :-(.

It's interesting though that your examples are all in v10 or older.
Could we have done something that indirectly fixes the problem
since then?  Or is that just chance?

			regards, tom lane