MIME-Version: 1.0
References: <Z5cDQJM9nnoXuStO@paquier.xyz> <Z5xTb5iBHVGns35R@paquier.xyz>
 <CAP53Pkw1QJHH9UDjkArS=XdAxtK7XWMpZLGHnVMDmhRTp_HYYw@mail.gmail.com>
 <Z5xgmgyV-wnzMpkO@paquier.xyz>
 <CAA5RZ0vM9AsEqvKued2drKZJ1opt3wbYaDbxGzi-khkNzwn7og@mail.gmail.com>
 <Z6Ks3ta5089DXiPc@paquier.xyz>
 <CAA5RZ0sfRbd1xcq_oHNA0TPr57yM8qkg-GoD6A0nUfyxZhs33Q@mail.gmail.com>
 <CAP53PkxocbNr+eRag3FEJp3-7S1U80FspOg8UQjO902TWMG=6A@mail.gmail.com>
 <CAA5RZ0u6yJdFL=p5vdpbZFS-2YY+Z6vtzmt4gejgZa3RcNiWMQ@mail.gmail.com>
 <404111766672953@mail.360.yandex.ru> <aU3CVSkKiyLwfreT@paquier.xyz>
 <CAP53PkyOB4kbYDoMXQaaN68rkU-Gt_Jw9iNzOgSwM4ULW-QrdQ@mail.gmail.com>
In-Reply-To: 
 <CAP53PkyOB4kbYDoMXQaaN68rkU-Gt_Jw9iNzOgSwM4ULW-QrdQ@mail.gmail.com>
From: Sami Imseih <samimseih@gmail.com>
Date: Thu, 19 Mar 2026 10:13:50 -0500
Message-ID: 
 <CAA5RZ0vpq5=W3PXAo_rVzpn6bMWONj4JK14iFE2BLenJKbtvFA@mail.gmail.com>
Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a
 query
To: Lukas Fittl <lukas@fittl.com>
Cc: Michael Paquier <michael@paquier.xyz>,
	=?UTF-8?B?0JDQvdC00YDQtdC5INCa0LDQt9Cw0YfQutC+0LI=?=
 <andrey.kazachkov@tantorlabs.ru>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Marko M <marko@pganalyze.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAA5RZ0vpq5%3DW3PXAo_rVzpn6bMWONj4JK14iFE2BLenJKbtvFA%40mail.gmail.com>
Precedence: bulk

> I missed this at the time, but happened to run across this by coincidence.
>
> Consider this a late +1 on the idea, i.e. I do think that emitting the
> plan ID as "plan identifier" in EXPLAIN seems reasonable when a plugin
> sets it - the cost is negligible, and it'd make it easier to work with
> extensions like pg_stat_plans.

FWIW, the per plan hooks introduced in 4fd02bf7cf94c can allow an extension
to emit the plan identifier in EXPLAIN as well.

--
Sami Imseih
Amazon Web Services (AWS)