Horton

Re: 039_end_of_wal: error in "xl_tot_len zero" test

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Rowley <dgrowleyml@gmail.com>
Cc: Thomas Munro <thomas.munro@gmail.com>, Anton Voloshin <a.voloshin@postgrespro.ru>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2024-05-12T21:39:36Z
Lists: pgsql-hackers 
David Rowley <dgrowleyml@gmail.com> writes:
> 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.

Hm.  It occurs to me that there *is* a system-specific component to
the amount of WAL emitted during initdb: the number of locales
that "locale -a" prints translates directly to the number of
rows inserted into pg_collation.  So maybe skimmer has a locale
set that's a bit different from anybody else's, and that's what
let it see this issue.

			regards, tom lane

Commits

  1. Stabilize 039_end_of_wal test.

  2. Create syscache entries for pg_extension