Re: [PATCH] Speed up pg_waldump TAP test and fix some GitHub CI Windows flakiness

From: Sehrope Sarkuni <sehrope(at)jackdb(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Speed up pg_waldump TAP test and fix some GitHub CI Windows flakiness
Date: 2026-09-02 00:18:45
Message-ID: CAH7T-apNC-M_2g6L3NDAukcBxNnTRe868ueMxP-jOgx-BxbSxg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 1, 2026 at 6:38 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> The differences between v2 and part1 are the two switches of
> $start_lsn to $contrecord_lsn, which don't matter as we want to check
> the end of the records. These moves cut already a lot of activity
> without touching coverage.
>
> Let's just do Nazir's v2 as a first step with a backpatch to ease the
> CI and buildfarm pain a bit.

Sounds good.

> Will apply that portion in a bit, that's worth its own weight in gold.

Thanks again to you both for looking at this. Was an interesting rabbit
hole to learn about why it's so much slower for Windows.

Will take another look at this later to see if if there's more to be
gained or similar low hanging fruit elsewhere in the suite.

Regards,
-- Sehrope Sarkuni
Founder & CEO | JackDB, Inc. | https://www.jackdb.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-09-02 00:35:03 Re: Logical replication row filter loses unchanged toasted columns
Previous Message Andres Freund 2026-09-02 00:05:12 Re: OOM kill during planning - pg_terminate_backend is ignored