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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Anton Voloshin <a(dot)voloshin(at)postgrespro(dot)ru>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 039_end_of_wal: error in "xl_tot_len zero" test
Date: 2024-05-06 02:51:25
Message-ID: CA+hUKGLKFgNC-byuNKmjGDLSx-C_tW+p=_R6MynBFzd-TcxTTw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 15, 2024 at 10:40 PM Anton Voloshin
<a(dot)voloshin(at)postgrespro(dot)ru> wrote:
> On 19/01/2024 01:35, Thomas Munro wrote:
> > I don't yet have an opinion on the best way to
> > do it though. Would it be enough to add emit_message($node, 0) after
> > advance_out_of_record_splitting_zone()?
>
> Yes, indeed that seems to be enough. At least I could not produce any
> more "xl_tot_len zero" failures with that addition.
>
> I like this solution the best.

Oh, it looks like this new build farm animal "skimmer" might be
reminding us about this issue:

https://buildfarm.postgresql.org/cgi-bin/show_history.pl?nm=skimmer&br=HEAD

I don't know why it changed, but since this is an LSN/page alignment
thing, it could be due to external things like an OS upgrade adding
more locales or something that affects initdb. Will look soon and
fix.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2024-05-06 03:01:30 Re: SQL:2011 application time
Previous Message Michael Paquier 2024-05-06 01:03:37 Re: Weird test mixup