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 1kYY9m-0001Ah-Jz for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 17:25:42 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kYY9k-0005Y0-IC for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 17:25:40 +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 1kYY9k-0005XH-C0 for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 17:25:40 +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 1kYY9h-0002pj-OH for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 17:25:39 +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 09UHPZMN099582; Fri, 30 Oct 2020 13:25:35 -0400 From: Tom Lane To: Heath Lord cc: pgsql-bugs@lists.postgresql.org Subject: Re: REL_13_STABLE Windows 10 Regression Failures In-reply-to: References: Comments: In-reply-to Heath Lord message dated "Fri, 30 Oct 2020 13:05:12 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <99580.1604078735.1@sss.pgh.pa.us> Date: Fri, 30 Oct 2020 13:25:35 -0400 Message-ID: <99581.1604078735@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Heath Lord writes: > When building from source on a Windows 10 VM using MinGW (8.1.0), I > get a random number of regression failures off the REL_13_STABLE > branch. I debugged this a little bit and found out that the "random" > number of failures is fully dependent on the machine and if I disable > the "stats_ext.sql" regression test; all other tests pass without > issue. When the "stats_ext.sql" regression test runs, it causes a > database exception and PostgreSQL crashes. Hmph ... it's weird that we have not seen this in the buildfarm. Have you tried to extract any info from the crash, like a stack trace? > I did some digging and determined that on the REL_13_STABLE branch > this instability was introduced with this commit > "b380484a850b6bf7d9fc0d85c555a2366e38451f"[1]. This corresponds to > commit "19f5a37b9fc48a12c77edafb732543875da2f4a3"[1] on master. I > worked backwards from there to determine when the regressions stopped > failing and determined that with commit > "be0a6666656ec3f68eb7d8e7abab5139fcd47012"[2] the regression tests are > no longer failing. I'm having a hard time believing that b380484a8 would have introduced a portability problem, and an even harder time believing that be0a66666 would have resolved it if so. What seems more likely is that there's some underlying issue such as a memory stomp, that the first commit accidentally exposed and the second one accidentally hid again. So, even if back-patching be0a66666 seemed feasible from a stability standpoint (which I don't think it is), I fear it'd just mask a problem that would eventually bite us again. So I think we need to dig down and try to identify the root cause, without any preconceptions about how to fix it. Again, a stack trace would be pretty useful. Or at least some info about which step of stats_ext.sql is crashing. regards, tom lane