Request a Demo
Home   >   mailing lists

Re: [PATCH] Optionally record Plan IDs to track plan changes for a query - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Date
Msg-id CAA5RZ0vpq5=W3PXAo_rVzpn6bMWONj4JK14iFE2BLenJKbtvFA@mail.gmail.com
Whole thread
In response to Re: [PATCH] Optionally record Plan IDs to track plan changes for a query  (Lukas Fittl <lukas@fittl.com>)
List pgsql-hackers
Tree view 
> 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)

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Feature freeze timezone change request
Next
From: Nathan Bossart
Date:
Subject: Re: Feature freeze timezone change request