From: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
---|---|
To: | Sami Imseih <samimseih(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-31 07:10:00 |
Message-ID: | 5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30/7/2025 22:09, Sami Imseih wrote:
> The concepts of custom and generic plan types are associated with plan caches,
> so they cannot have a different source. right?
That is exactly what confused me: what does the 'origin' of the plan
mean? See the comment:
> PlannedStmtOrigin identifies from where a PlannedStmt comes from.
The first thing that comes to mind after reading this comment is a
subsystem, such as the SPI, simple or extended protocol, or an
extension. Another meaning is a type of plan, such as 'custom',
'generic', or 'referenced'. As I see, here is a bit different
classification used, not so obvious, at least for me.
--
regards, Andrei Lepikhov
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2025-07-31 07:16:35 | Re: track generic and custom plans in pg_stat_statements |
Previous Message | Andrey Borodin | 2025-07-31 06:29:25 | Re: IPC/MultixactCreation on the Standby server |