Re: XLogReadRecord() error in XlogReadTwoPhaseData() - Mailing list pgsql-hackers

From Tom Lane
Subject Re: XLogReadRecord() error in XlogReadTwoPhaseData()
Date
Msg-id 1787748.1642991104@sss.pgh.pa.us
Whole thread Raw
In response to Re: XLogReadRecord() error in XlogReadTwoPhaseData()  (Michael Paquier <michael@paquier.xyz>)
Responses Re: XLogReadRecord() error in XlogReadTwoPhaseData()
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Sun, Jan 23, 2022 at 06:10:07PM -0800, Noah Misch wrote:
>> Could do that.  Every run that doesn't get the flaky failure will print a
>> message like "TODO passed:  3-5", though the test file could mitigate that by
>> declaring the TODO only on configurations where we expect a failure.  The
>> 027_stream_regress.pl trouble involves reaching a die(), not failing a test in
>> this sense, so that one would take more work.

> Using a TODO has the advantage to allow the tests to run on a periodic
> basis, even if they could fail in this unexpected way.

I'm okay with this *if* the TODO marking can be constrained to platforms
where we know there's a problem.  Otherwise I'm afraid it will mask
unexpected problems.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: XLogReadRecord() error in XlogReadTwoPhaseData()
Next
From: Michael Paquier
Date:
Subject: Re: Bogus duplicate command issued in pg_dump