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

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
Subject: Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash
Date: 2026-10-14 23:02:59
Message-ID: CAN4CZFPA-ZztOLwr5MnTx9NZGwgt8Pf=qQbSzGCGhRa=61-mvw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> FWIW, I am not convinced that the gain in coverage is worth the cycles
> on this one. This is only one WARNING with many more patterns to
> check how pgstat_read_statsfile() is robust with changes in
> shared_preload_libraries and reuses of the same IDs.

I agree, I included the test mainly because it's an easy reproducer
for the issue, otherwise it's very specific. I only kept it as a
single patch because the entire thing is small and it is easy to
separate the pgstat.c changes from it.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sami Imseih 2026-10-14 23:22:29 Re: pgstat: allow a stats kind to use its own dedicated dsa/dshash
Previous Message David Rowley 2026-10-14 23:00:57 Re: Reducing relcache memory usage: deduping index shapes