Re: track generic and custom plans in pg_stat_statements

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>
Cc: Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Nikolay Samokhvalov <nik(at)postgres(dot)ai>
Subject: Re: track generic and custom plans in pg_stat_statements
Date: 2025-06-05 21:07:44
Message-ID: CAA5RZ0v4Lqc3KOzFCOJd0hjBpF10W=-E6xn0z_HizZY9uxPR0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Thanks for your work on this.
>
> Since we've changed the placement of these parameters
> between parallel_workers and stats_since, we should also update
> the documentation to reflect their new location.

Absolutely. My miss. Here is v9 with the doc updated.

Thanks!

--
Sami

Attachment Content-Type Size
v9-0001-Add-plan_cache-counters-to-pg_stat_statements.patch application/octet-stream 37.1 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2025-06-05 21:23:03 Re: Question Regarding Merge Append and Parallel Execution of Index Scans on Partitioned Table
Previous Message Jeff Davis 2025-06-05 20:57:15 Re: [19] Proposal: function markers to indicate collation/ctype sensitivity