| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | zhouenbing <zhouenbing(at)sunwoda-evb(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: empty,query_id, pg_stat_activity |
| Date: | 2025-09-03 20:54:27 |
| Message-ID: | CAKAnmmL=dtnV5JxmrJNM=dFnQXRb6U3ah0E=bwxSD_+iDPv=ag@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Sep 2, 2025 at 10:01 PM zhouenbing <zhouenbing(at)sunwoda-evb(dot)com>
wrote:
> No, if the query_id I provided is empty, it indicates that the statement
> session is in an active state, meaning the operation is ongoing
>
The session is active, but there is no I/O yet, as the query has arrived,
but has not been parsed yet. The queryid appears right before the query
actually executes, so a lack of queryid is a safe indicator that the query
is not actually doing any work yet- it's still spinning up. From a
performance monitoring standpoint, you should be safe to exclude rows with
no queryid.
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2025-09-03 20:58:08 | Re: BUG #19042: Option --help not recognized at the end of command line in pg_restore |
| Previous Message | Tom Lane | 2025-09-03 20:10:52 | Re: BUG #18960: Mistake in test test_simple_pipeline (libpq_pipeline.c) |