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 1kUDUi-0004hX-Fr for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 18:33:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kUDUf-0005va-55 for pgsql-hackers@arkaria.postgresql.org; Sun, 18 Oct 2020 18:33:21 +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 1kUDUe-0005ud-UV for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 18:33:20 +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 1kUDUc-0003Xv-Sk for pgsql-hackers@lists.postgresql.org; Sun, 18 Oct 2020 18:33:20 +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 09IIXEUN231287; Sun, 18 Oct 2020 14:33:14 -0400 From: Tom Lane To: Alexander Lakhin cc: Victor Spirin , pgsql-hackers@lists.postgresql.org Subject: Re: Sometimes the output to the stdout in Windows disappears In-reply-to: References: <4124040.1598898684@sss.pgh.pa.us> <855416.1600022228@sss.pgh.pa.us> <4156857.1602865112@sss.pgh.pa.us> <117919.1602949857@sss.pgh.pa.us> <132799.1602960277@sss.pgh.pa.us> Comments: In-reply-to Alexander Lakhin message dated "Sun, 18 Oct 2020 21:00:00 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <231285.1603045994.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 18 Oct 2020 14:33:14 -0400 Message-ID: <231286.1603045994@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Alexander Lakhin writes: > I've made a simple cmd script to reproduce problems seen on dory: > ... > Without the fix I've got errors on iterations 43, 46, 128, 47, 14, 4, > 27, which approximately corresponds to the ECPG-Check failure frequency > on dory (for HEAD). > With the fix all the 200 iterations passed as expected. > Then I ran the loop again just to be sure and got: > test thread/descriptor=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0 ... stderr FAILED=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 81 m= s > iteration 124 failed. I had been thinking we'd have to wait a month or two for the buildfarm to accumulate enough runs to be confident in whether the WSACleanup removal fixes the ecpg failures. However, now that you did this experiment, I think we have enough evidence already that it fixes it (or at least makes things an order of magnitude better). So now I'm inclined to not wait, but go ahead and backpatch 7d00a6b2d now. There's still enough time before the November releases that we can expect that any nasty problems will show up in the buildfarm before we ship. regards, tom lane