Re: track generic and custom plans in pg_stat_statements

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Andrei Lepikhov <lepihov(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>
Subject: Re: track generic and custom plans in pg_stat_statements
Date: 2025-07-28 20:57:02
Message-ID: CAA5RZ0vtxE2z0AsKwaTT2hOd3iBnq_NeVe3ea2dg=Uz_TSWzAQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> The current pg_stat_statements change may be a
> good example of the employment of such infrastructure, isn't it?

So, the current set of patches now will help move forward the specific
use-case of this thread. If we need something different that will be
useful for more use-cases, perhaps it's better to start a new thread as
a follow-up to this? I think there may be more debate on what that
looks like.

--
Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-07-28 20:57:54 Re: [WIP]Vertical Clustered Index (columnar store extension) - take2
Previous Message Jacob Champion 2025-07-28 20:52:42 Re: [PATCH] OAuth: fix performance bug with stuck multiplexer events