| From: | "zhouenbing" <zhouenbing(at)sunwoda-evb(dot)com> |
|---|---|
| To: | <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | 答复: Empty query_id in pg_stat_activity |
| Date: | 2025-08-13 09:52:53 |
| Message-ID: | 000501dc0c38$09b76cb0$1d264610$@sunwoda-evb.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Maile address:
https://www.postgresql.org/message-id/ed81b882-2bef-47e8-95af-3a55ddf28e18@e
wie.name
发件人: zhouenbing [mailto:zhouenbing(at)sunwoda-evb(dot)com]
发送时间: 2025-08-13 17:50
收件人: 'pgsql-bugs(at)lists(dot)postgresql(dot)org' <pgsql-bugs(at)lists(dot)postgresql(dot)org>
主题: Empty query_id in pg_stat_activity
I see that the Message ID is' ae6ef509-7bba-4d5b-aac4-82def6797e61(at)ewie(dot)name
<mailto:ae6ef509-7bba-4d5b-aac4-82def6797e61(at)ewie(dot)name> The email states
that the bug with an empty query_id has been fixed in versions
14.14/15.9/16.5/17.1. However, when I tested versions 15.4/15.9/17.4 using
the pebench-M=simple | extended tool, I still encountered the issue of an
empty query_id. This has caused some related problems in tracking
performance issues on Postgres. Is this a testing problem or is the bug
indeed present?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2025-08-13 09:59:50 | Re: "unexpected duplicate for tablespace" problem in logical replication |
| Previous Message | zhouenbing | 2025-08-13 09:50:29 | Empty query_id in pg_stat_activity |