Re: Improve pg_stat_statements scalability

From: Lukas Fittl <lukas(at)fittl(dot)com>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improve pg_stat_statements scalability
Date: 2026-05-23 01:15:00
Message-ID: CAP53PkyWD99bNwFVv2KibfL4bhm-D78QAnc9UqQQJdtJ3mQWPQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 21, 2026 at 9:38 PM Lukas Fittl <lukas(at)fittl(dot)com> wrote:
>
> On Mon, May 11, 2026 at 4:54 PM Sami Imseih <samimseih(at)gmail(dot)com> wrote:
> > pg_stat_statements has well-known scaling problems under
> > high concurrency. This patch series is an initial proposal
> > for how to $SUBJECT.
>
> Agreed. Let's fix this for Postgres 20.
>
> Thank you for putting together initial patches!

For archive's sake and others reading along, we had a productive
discussion about this today at PGConf.Dev.

I've created a new wiki page combining the prior 2025 discussion, and
notes from today:

https://wiki.postgresql.org/wiki/Scalability_of_pg_stat_statements

Thanks,
Lukas

--
Lukas Fittl

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Japin Li 2026-05-23 01:40:39 Re: Report oldest xmin source when autovacuum cannot remove tuples
Previous Message Chengpeng Yan 2026-05-23 01:14:09 Re: [PATCH] Fix overflow and underflow in regr_r2()