| From: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | "duomi(dot)peng" <duomi(dot)peng(at)qq(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: bug reapper: Empty query_id in pg_stat_activity |
| Date: | 2025-08-28 12:28:10 |
| Message-ID: | CAFC+b6qwZ9zkWjNy+km7xkF2VvM+T=ye5+PCeCmpjagtFLPX0g@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Aug 28, 2025 at 5:55 PM Srinath Reddy Sadipiralla <
srinath2133(at)gmail(dot)com> wrote:
> sorry for half cooked analysis ,the reason is pgstat_report_query_id()
> zeroes st_query_id before the new one is computed in exec_simple_query(). A
> concurrent reader of pg_stat_activity during that narrow timing gap
> observes 0 (displayed as NULL). The fix I tried is to retain the previous
> query_id (prev_st_query_id) and return it when st_query_id is still 0 but
> query_id computation is enabled, thoughts?
>
I was able to reproduce this on 15.14 and master also , I think we have to
backpatch the fix.
--
Thanks,
Srinath Reddy Sadipiralla
EDB: https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-08-28 12:42:32 | Re: bug reapper: Empty query_id in pg_stat_activity |
| Previous Message | Srinath Reddy Sadipiralla | 2025-08-28 12:25:27 | Re: bug reapper: Empty query_id in pg_stat_activity |