| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PROPOSAL] Detecting plan changes with plan_id in pg_stat_activity |
| Date: | 2022-06-16 05:48:34 |
| Message-ID: | 8f0bdf9d-2110-8e36-60be-1520fe3b52f6@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 15/6/2022 21:45, Imseih (AWS), Sami wrote:
> Adding a plan_id to pg_stat_activity allows users
> to determine if a plan for a particular statement
> has changed and if the new plan is performing better
> or worse for a particular statement.
> There are several ways the plan_id in pg_stat_activity
In general, your idea is quite useful.
But, as discussed earlier [1] extensions would implement many useful
things if they could add into a plan some custom data.
Maybe implement your feature with some private list of nodes in plan
structure instead of single-purpose plan_id field?
[1]
https://www.postgresql.org/message-id/flat/e0de3423-4bba-1e69-c55a-f76bf18dbd74%40postgrespro.ru
--
regards,
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2022-06-16 05:49:15 | Re: Extending USING [heap | mytam | yourtam] grammar and behavior |
| Previous Message | Mark Dilger | 2022-06-16 05:23:36 | Re: Modest proposal to extend TableAM API for controlling cluster commands |