Re: Fixing WAL instability in various TAP tests
Tom Lane <tgl@sss.pgh.pa.us>
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-25T14:17:47Z
Lists: pgsql-hackers
Mark Dilger <mark.dilger@enterprisedb.com> writes: >> On Sep 24, 2021, at 10:21 PM, Noah Misch <noah@leadboat.com> wrote: >>> I would >>> expect tests which fail under legal alternate GUC settings to be hardened to >>> explicitly set the GUCs as they need, rather than implicitly relying on the >>> defaults. >> That is not the general practice in PostgreSQL tests today. The buildfarm >> exercises some settings, so we keep the tests clean for those. Coping with >> max_wal_size=2 that way sounds reasonable. I'm undecided about the value of >> hardening tests against all possible settings. > Leaving the tests brittle wastes developer time. Trying to make them proof against all possible settings would waste a lot more time, though. regards, tom lane
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