On Wed, Feb 05, 2025 at 09:06:24PM -0500, Tom Lane wrote: > Basically, this test is broken because it assumes that the server > is freshly started. That's not a scenario the buildfarm runs > the core tests under, unfortunately, but it is one commonly > used in hand testing.
Right. You are pointing at a stability issue related to the reads.
While looking at your case, I am also able to see two additional
failures with io_sum_wal_init_writes and io_sum_wal_init_fsyncs with
the initial context.
The queries for the normal context are not going to have this problem
even if we have a pg_stat_reset_shared('io'), but the init context
gets unstable, unfortunately. I don't see a way through here in the
main regression test suite, so how about moving these into
027_stream_regress.pl. It is possible to query the WAL read on the
standby of this test, and the write part for the init context on the
primary. The syncs are not relevant as TAP usually runs with
fsync=off, so better to remove this part entirely.
--
Michael
signature.asc
Description: PGP signature
