Re: Fixing WAL instability in various TAP tests
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Mark Dilger <mark.dilger@enterprisedb.com>, Noah Misch <noah@leadboat.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2021-09-27T23:43:13Z
Lists: pgsql-hackers
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. -- Michael
Commits
-
Fix instability in contrib/bloom TAP tests.
- cf26a8d8a75f 13.5 landed
- cea5624f6a23 14.1 landed
- 6bc6bd47cf71 15.0 landed
- 2d8a8b18fe5a 12.9 landed
-
Re-enable contrib/bloom's TAP tests.
- 7d1aa6bf1c27 15.0 landed