pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Noah Misch <noah@leadboat.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: Fixing WAL instability in various TAP tests
Date: Mon, 27 Sep 2021 22:20:12 -0400
Message-ID: <2801531.1632795612@sss.pgh.pa.us> (raw)
In-Reply-To: <YVJXEf119KrJDFdq@paquier.xyz>
References: <32A1FDD1-9C7B-43B1-B3EE-49198DD3F887@enterprisedb.com>
	<20210925052151.GA4082552@rfd.leadboat.com>
	<2E9D28A3-1B54-446B-AC12-3BF86A2B522A@enterprisedb.com>
	<2502590.1632579467@sss.pgh.pa.us>
	<2B4C64CF-EE3F-474B-9685-6A927E5E49AE@enterprisedb.com>
	<20210925160039.GA4134968@rfd.leadboat.com>
	<193AC968-C348-4D81-88BC-384560F87500@enterprisedb.com>
	<C1D227C2-C271-4310-8C85-C5368C298622@enterprisedb.com>
	<2769443.1632773967@sss.pgh.pa.us>
	<YVJXEf119KrJDFdq@paquier.xyz>

Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Sep 27, 2021 at 04:19:27PM -0400, Tom Lane wrote:
>> I tried the same thing (i.e., re-enable bloom's TAP test) on my laptop
>> just now, and it passed fine.  The laptop is not exactly the same
>> as longfin was in 2018, but it ought to be close enough.  Not sure
>> what to make of that --- maybe the failure is only intermittent,
>> or else we fixed the underlying issue since then.

> Honestly, I have no idea what change in the backend matters here.  And
> it is not like bloom has changed in any significant way since d3c09b9.

I went so far as to check out 03faa4a8dd on longfin's host, and I find
that I cannot reproduce the failure shown at

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=longfin&dt=2018-11-25+23%3A59%3A03

So that's the same hardware, and identical PG source tree, and different
results.  This seems to leave only two theories standing:

1.  It was a since-fixed macOS bug.  (Unlikely, especially if we also saw
it on other platforms.)

2.  The failure manifested only in the buildfarm, not under manual "make
check".  This is somewhat more plausible, especially since subsequent
buildfarm script changes might then explain why it went away.  But I have
no idea what the "subsequent script changes" might've been.

			regards, tom lane





view thread (25+ messages)  latest in thread

Message-ID: <2801531.1632795612@sss.pgh.pa.us>
Permalink:  ../2801531.1632795612@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2801531.1632795612@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, andrew@dunslane.net, mark.dilger@enterprisedb.com, noah@leadboat.com
  Subject: Re: Fixing WAL instability in various TAP tests
  In-Reply-To: <2801531.1632795612@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox