Re: Fixing WAL instability in various TAP tests - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Fixing WAL instability in various TAP tests
Date
Msg-id 2502590.1632579467@sss.pgh.pa.us
Whole thread Raw
In response to Re: Fixing WAL instability in various TAP tests  (Mark Dilger <mark.dilger@enterprisedb.com>)
Responses Re: Fixing WAL instability in various TAP tests
List 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



pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: Fixing WAL instability in various TAP tests
Next
From: Fabien COELHO
Date:
Subject: Re: rand48 replacement