Re: track generic and custom plans in pg_stat_statements

From: Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>
To: Sami Imseih <samimseih(at)gmail(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 20:47:23
Message-ID: 60f09467-bfe6-49bc-a47a-fe887050a23a@tantorlabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 03.06.2025 06:31, Sami Imseih wrote:
> See v8 with the field names reorganized.

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.

--
Best regards,
Ilia Evdokimov,
Tantor Labs LLC.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2025-06-05 20:52:45 Re: track generic and custom plans in pg_stat_statements
Previous Message Jeff Davis 2025-06-05 20:47:22 Re: [19] Proposal: function markers to indicate collation/ctype sensitivity