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

From: Sehrope Sarkuni <sehrope(at)jackdb(dot)com>
To: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, 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-01 16:32:50
Message-ID: CAH7T-arZ9CDvkGY=9Sa8sPLySyZHXmMTYtkaq_8pATqicRMnKQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 1, 2026 at 11:37 AM Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> wrote:
> I haven't checked the patches yet but for this problem I generally
> select any other long-running test and try to normalize test timings.

Oh that's a good idea. I'll try it like that next to get a better read.

In the meantime, I tried your v2 on the same linux box v.s. the rest:

time stdout decoded per decoded
(mean) via IPC archive scenario total
master 4.51s 139.1 MB 109.8 MB 393.5 MB
v2 3.78s 37.5 MB 74.2 MB 222.5 MB
part1 3.74s 57.7 MB 91.1 MB 273.4 MB
part2 3.19s 37.1 MB 42.6 MB 127.8 MB
part3 2.52s 19.4 MB 10.8 MB 64.2 MB

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-09-01 16:41:08 Re: pgstat: Flush some statistics within running transactions, take 2
Previous Message Nathan Bossart 2026-09-01 16:26:39 Re: [PATCH] Remove dead code in pg_dump