Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash
Date: 2026-10-19 05:00:00
Message-ID: 16e486c8-a559-4bd9-bb8c-fb423396f259@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Michael,

19.10.2026 01:09, Michael Paquier wrote:
> On Sun, Oct 18, 2026 at 10:00:00AM +0300, Alexander Lakhin wrote:
>> But there are also several tests that need extra care:
>> src/bin/pg_basebackup/t/030_pg_recvlogical.pl
>> src/test/modules/test_aio/t/004_read_stream.pl
>> src/test/modules/test_checksums/t/003_standby_restarts.pl
>> src/test/recovery/t/007_sync_rep.pl
>> src/test/recovery/t/040_standby_failover_slots_sync.pl
>> src/test/recovery/t/048_vacuum_horizon_floor.pl
>> contrib/test_decoding/t/001_repl_stats.pl
> Do we have the buildfarm complaining about any of these? I cannot get
> excited to act without a reason to do so.

I haven't seen failures of those tests on buildfarm so far (probably
disproportional slowdown of an exiting backend while a TAP test itself
runs fast is not that common on buildfarm), but as funny things happen
from time to time, hippopotamus produced the first failure of
003_standby_restarts.pl just one hour after you asked: [1].

Maybe it has an unrelated cause, though. I'm going to examine this
closer and report to Daniel in a separate thread.

Thank you for the reply!

[1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=hippopotamus&dt=2026-10-18%2022%3A15%3A04

Best regards,
Alexander

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2026-10-19 05:25:40 Re: [PATCH v1] Batch B-tree TIDs when building a bitmap
Previous Message Vaibhav Dalvi 2026-10-19 04:13:51 Re: walreceiver: stale hot_standby_feedback xmin on primary when wal_receiver_status_interval = 0 (PG16 and later)