Re: Redesign per-backend statistics - Mailing list pgsql-hackers

From Bertrand Drouvot
Subject Re: Redesign per-backend statistics
Date
Msg-id arDZoI/5xHU2utRh@bdtpg
Whole thread
In response to Re: Redesign per-backend statistics  (Bertrand Drouvot <bertranddrouvot.pg@gmail.com>)
Responses Re: Redesign per-backend statistics
List pgsql-hackers
Hi,

On Thu, Aug 13, 2026 at 03:41:58PM +0000, Bertrand Drouvot wrote:
> Hi,
> 
> On Mon, Aug 10, 2026 at 02:45:16PM +0000, Bertrand Drouvot wrote:
> > Given that the cost is still sub millisecond at hundreds of connections and a few
> > milliseconds at 10000 and given the impact mentioned above, I don't think this is
> > a practical blocker though. What do you think?
> > 
> 
> A rebase was needed, so while at it, I implemented what we have discussed so far,
> means:
> 
> - moved the generic per-backend statistics infrastructure to a new pgstat_per_backend.c
> file
> - split the previous 0005 into the IO migration and the removal of PGSTAT_KIND_BACKEND
> and pgstat_backend.c.

PFA another mandatory rebase (tiny change to test_misc/meson.build).

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Attachment

pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: WAL segment file descriptor leak on read errors can PANIC the server
Next
From: Heikki Linnakangas
Date:
Subject: Re: [Patch] Fix pg_get_multixact_stats() over-reporting members on a hot standby