Re: [PATCH] Optionally record Plan IDs to track plan changes for a query

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Lukas Fittl <lukas(at)fittl(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Андрей Казачков <andrey(dot)kazachkov(at)tantorlabs(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Marko M <marko(at)pganalyze(dot)com>
Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Date: 2026-03-19 15:13:50
Message-ID: CAA5RZ0vpq5=W3PXAo_rVzpn6bMWONj4JK14iFE2BLenJKbtvFA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-19 15:14:05 Re: Feature freeze timezone change request
Previous Message Andrew Dunstan 2026-03-19 15:07:27 Re: Feature freeze timezone change request