| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Sami Imseih <samimseih(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, kaido vaikla <kaido(dot)vaikla(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: query_id, pg_stat_activity, extended query protocol |
| Date: | 2024-09-18 05:48:13 |
| Message-ID: | ZuppnZgCWI1954Ie@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Sep 18, 2024 at 09:38:32AM +0900, Michael Paquier wrote:
> FWIW, I was thinking about something like what has been done in
> indexcmds.c for 5bbdfa8a18dc as the query ID value is not predictible
> across releases, but we could see whether it is set or not.
By the way, with the main issue fixed as of 933848d16dc9, could it be
possible to deal with the plan cache part in a separate thread? This
is from the start a separate thread to me, and we've done quite a bit
here already.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | shveta malik | 2024-09-18 06:03:08 | Re: Add contrib/pg_logicalsnapinspect |
| Previous Message | Michael Paquier | 2024-09-18 05:46:32 | Re: query_id, pg_stat_activity, extended query protocol |