public inbox for pgsql-hackers@postgresql.org  

help / color / mirror / Atom feed

From: Lukas Fittl <lukas@fittl.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Improve pg_stat_statements scalability
Date: Fri, 22 May 2026 18:15:00 -0700
Message-ID: <CAP53PkyWD99bNwFVv2KibfL4bhm-D78QAnc9UqQQJdtJ3mQWPQ@mail.gmail.com> (raw)
In-Reply-To: <CAP53Pky9CViOfy1yQxJv0VE7aEiuDb13SppwGa7T_qOeBSumfA@mail.gmail.com>
References: <CAA5RZ0vZwR_dSK6fo0P2-EnskUVN0NjLHnGnJMFDPC8-kEW3sQ@mail.gmail.com>
	<CAP53Pky9CViOfy1yQxJv0VE7aEiuDb13SppwGa7T_qOeBSumfA@mail.gmail.com>

On Thu, May 21, 2026 at 9:38 PM Lukas Fittl <lukas@fittl.com> wrote:
>
> On Mon, May 11, 2026 at 4:54 PM Sami Imseih <samimseih@gmail.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

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: lukas@fittl.com, samimseih@gmail.com
  Subject: Re: Improve pg_stat_statements scalability
  In-Reply-To: <CAP53PkyWD99bNwFVv2KibfL4bhm-D78QAnc9UqQQJdtJ3mQWPQ@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox