Re: 039_end_of_wal: error in "xl_tot_len zero" test - Mailing list pgsql-hackers

From David Rowley
Subject Re: 039_end_of_wal: error in "xl_tot_len zero" test
Date
Msg-id CAApHDvqjviT1zwums=XSGDh_=w5_rYhnHGCD=Dwpj7A7bzWvvg@mail.gmail.com
Whole thread Raw
In response to Re: 039_end_of_wal: error in "xl_tot_len zero" test  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 039_end_of_wal: error in "xl_tot_len zero" test
List pgsql-hackers
On Mon, 6 May 2024 at 15:06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> My best guess is that that changed the amount of WAL generated by
> initdb just enough to make the problem reproduce on this animal.
> However, why's it *only* happening on this animal?  The amount of
> WAL we generate isn't all that system-specific.

I'd say that's a good theory as it's now passing again [1] after the
recent system_views.sql change done in 521a7156ab.

David

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=skimmer&dt=2024-05-06%2017%3A43%3A38



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: elog/ereport VS misleading backtrace_function function address
Next
From: Alexander Korotkov
Date:
Subject: Re: [PATCH] Improve amcheck to also check UNIQUE constraint in btree index.