pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Andrei Lepikhov <lepihov@gmail.com>
To: Sami Imseih <samimseih@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Sabino Mullane <htamfids@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: Nikolay Samokhvalov <nik@postgres.ai>
Cc: Ilia Evdokimov <ilya.evdokimov@tantorlabs.com>
Subject: Re: track generic and custom plans in pg_stat_statements
Date: Thu, 31 Jul 2025 09:10:00 +0200
Message-ID: <5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@gmail.com> (raw)
In-Reply-To: <CAA5RZ0t-5LjHFsYML49Dg=gt97GJbMs1zVGi86YDmvsa4=oGFw@mail.gmail.com>
References: <CAA5RZ0sxC0=2wZ-QaRB7FdMmQ4_BYKG=X+gdDGHnS6KTrfgLQA@mail.gmail.com>
	<1673684.1753379027@sss.pgh.pa.us>
	<CAA5RZ0sQuoHJsGc-dJV15yYURuXsOp2pwr9hLAk+pcm7=MAK2w@mail.gmail.com>
	<aILaHupXbIGgF2wJ@paquier.xyz>
	<CAA5RZ0t54uP+O2dGZCoYfzOU_wcT2trVL65GdZB00RiLDs9BCg@mail.gmail.com>
	<1933906.1753462272@sss.pgh.pa.us>
	<CAA5RZ0t4A4PVLHK5DPZWCsZvtviLf==PGG5eiy6Bm0DCpchHyQ@mail.gmail.com>
	<aIcWKh8wK2GWFMFz@paquier.xyz>
	<CAA5RZ0t6GctNqFA60_ajhw0D+9DeuHYa7F2QCQMumTxx=h3UZQ@mail.gmail.com>
	<CAA5RZ0sYd6-KeQqR4uLFS1swBh37jKJCzR_E-G373EuLKm5UzA@mail.gmail.com>
	<aInHvKN4Gsztmopy@paquier.xyz>
	<87249b23-c4c5-4c0b-88d3-efb13b8a04d1@gmail.com>
	<CAA5RZ0sgLNBKUdceqvoxNCbn9rirJhH6bUjAmSZB6557cbcG4Q@mail.gmail.com>
	<b3b87daa-d610-424d-8217-bc4a47dd918c@gmail.com>
	<CAA5RZ0t-5LjHFsYML49Dg=gt97GJbMs1zVGi86YDmvsa4=oGFw@mail.gmail.com>

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





view thread (73+ messages)  latest in thread

Message-ID: <5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@gmail.com>
Permalink:  ../5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@gmail.com/
Also on:    postgresql.org/message-id/5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@gmail.com

 · 

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: lepihov@gmail.com, samimseih@gmail.com, michael@paquier.xyz, tgl@sss.pgh.pa.us, htamfids@gmail.com, nik@postgres.ai, ilya.evdokimov@tantorlabs.com
  Subject: Re: track generic and custom plans in pg_stat_statements
  In-Reply-To: <5d6806ac-d74b-4563-9fc5-a7f0958b4ba2@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox