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 1myNk5-00030f-Lp for pgsql-hackers@arkaria.postgresql.org; Sat, 18 Dec 2021 00:38:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1myNk2-0000Sv-Mg for pgsql-hackers@arkaria.postgresql.org; Sat, 18 Dec 2021 00:38:26 +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 1myNk2-0000Sl-Dg for pgsql-hackers@lists.postgresql.org; Sat, 18 Dec 2021 00:38:26 +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 1myNk0-0003yh-4T for pgsql-hackers@postgresql.org; Sat, 18 Dec 2021 00:38:25 +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 1BI0cDFS1431257; Fri, 17 Dec 2021 19:38:13 -0500 From: Tom Lane To: Greg Stark cc: Thomas Munro , Tomas Vondra , Daniel Gustafsson , Stephen Frost , Alvaro Herrera , Andres Freund , David Steele , Dmitry Dolgov <9erthalion6@gmail.com>, Jakub Wartak , Tomas Vondra , pgsql-hackers Subject: Re: WIP: WAL prefetch (another approach) In-reply-to: References: <8dd2dcc2-0b6b-a4ab-c1b3-032c0a5ab1c3@enterprisedb.com> <773932.1619022622@sss.pgh.pa.us> <5B6070FF-5869-4A84-88BC-2D04EDCDB858@yesql.se> <477464.1637981215@sss.pgh.pa.us> <13! 70655.1639767599@sss.pgh.pa.us> <1374737.1639770826@sss.pgh.pa.us> <1426276.1639784421@sss.pgh.pa.us> Comments: In-reply-to Greg Stark message dated "Fri, 17 Dec 2021 18:55:50 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1431255.1639787893.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Fri, 17 Dec 2021 19:38:13 -0500 Message-ID: <1431256.1639787893@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Greg Stark writes: > But the bigger question is. Are we really concerned about this flaky > problem? Is it worth investing time and money on? I can get money to > go buy a G4 or G5 and spend some time on it. It just seems a bit... > niche. But if it's a real bug that represents something broken on > other architectures that just happens to be easier to trigger here it > might be worthwhile. TBH, I don't know. There seem to be three plausible explanations: 1. Flaky hardware in my unit. 2. Ancient macOS bug, as Andres suggested upthread. 3. Actual PG bug. If it's #1 or #2 then we're just wasting our time here. I'm not sure how to estimate the relative probabilities, but I suspect #3 is the least likely of the lot. FWIW, I did just reproduce the problem on that machine with current HEAD: 2021-12-17 18:40:40.293 EST [21369] FATAL: inconsistent page found, rel 1= 663/167772/2673, forknum 0, blkno 26 2021-12-17 18:40:40.293 EST [21369] CONTEXT: WAL redo at C/3DE3F658 for B= tree/INSERT_LEAF: off 208; blkref #0: rel 1663/167772/2673, blk 26 FPW 2021-12-17 18:40:40.522 EST [21365] LOG: startup process (PID 21369) exit= ed with exit code 1 That was after only five loops of the regression tests, so either I got lucky or the failure probability has increased again. In any case, it seems clear that the problem exists independently of Munro's patches, so I don't really think this question should be considered a blocker for those. regards, tom lane