Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWUxo-0003nc-1X for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Mar 2022 03:13:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nWUxm-0001lK-Vb for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Mar 2022 03:13:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWUxm-0001io-Lu for pgsql-hackers@lists.postgresql.org; Tue, 22 Mar 2022 03:13:38 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nWUxj-0006o7-8i for pgsql-hackers@postgresql.org; Tue, 22 Mar 2022 03:13:38 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 22M3DVm12452112; Mon, 21 Mar 2022 23:13:31 -0400 From: Tom Lane To: Thomas Munro cc: Noah Misch , Alexander Lakhin , Andrew Dunstan , pgsql-hackers Subject: Re: Why is src/test/modules/committs/t/002_standby.pl flaky? In-reply-to: References: <1609152.1641691036@sss.pgh.pa.us> <3b904d7b-ef84-6f1b-9326-9f88c1374eb8@gmail.com> <5d507424-13ce-d19f-2f5d-ab4c6a987316@gmail.com> <2411751.1641849927@sss.pgh.pa.us> <20220319084704.GB2822749@rfd.leadboat.com> Comments: In-reply-to Thomas Munro message dated "Tue, 22 Mar 2022 15:16:06 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2452110.1647918811.1@sss.pgh.pa.us> Date: Mon, 21 Mar 2022 23:13:31 -0400 Message-ID: <2452111.1647918811@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Thomas Munro writes: > I have a new socket abstraction patch that should address the known > Windows socket/event bugs, but it's a little bigger than I thought it > would be, not quite ready, and now too late to expect people to review > for 15, so I think it should go into the next cycle. I've bounced > https://commitfest.postgresql.org/37/3523/ into the next CF. We'll > need to do something like 75674c7e for master. OK. You want me to push 75674c7e to HEAD? regards, tom lane