| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, 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>, 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-10-01 19:00:00 |
| Message-ID: | a1c7787c-9816-1376-311c-f3b8e32d633a@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Michael,
01.10.2024 05:07, Michael Paquier wrote:
> On Mon, Sep 30, 2024 at 10:07:55AM +0900, Michael Paquier wrote:
> ...
> And done this part.
If I'm not missing something, all the patches discussed here are committed
now, so maybe I've encountered a new anomaly.
Please try the following script:
BEGIN;
PREPARE s AS SELECT 1;
SELECT $1 \bind 1 \g
EXECUTE s;
It produces for me:
TRAP: failed Assert("!IsQueryIdEnabled() || !pgstat_track_activities || !debug_query_string || pgstat_get_my_query_id()
!= 0"), File: "execMain.c", Line: 423, PID: 1296466
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jacob Champion | 2024-10-01 19:04:53 | Re: pg_parse_json() should not leak token copies on failure |
| Previous Message | Masahiko Sawada | 2024-10-01 18:55:48 | Re: pg_trgm comparison bug on cross-architecture replication due to different char implementation |