Horton

Re: Fixing WAL instability in various TAP tests

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mark Dilger <mark.dilger@enterprisedb.com>
Cc: Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-09-27T22:49:31Z
Lists: pgsql-hackers 
Mark Dilger <mark.dilger@enterprisedb.com> writes:
>> On Sep 27, 2021, at 1:19 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I'm a little inclined to re-enable the test without your other
>> changes, just to see what happens.

> That sounds like a good idea.  Even if it passes at first, I'd prefer to leave it for a week or more to have a better sense of how stable it is.  Applying my patches too soon would just add more variables to a not-so-well understood situation.

Done.  I shall retire to a safe viewing distance and observe the
buildfarm.

			regards, tom lane

Commits

  1. Fix instability in contrib/bloom TAP tests.

  2. Re-enable contrib/bloom's TAP tests.