| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Lichtenberger <r(dot)lichtenberger(at)synedra(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_stat_activity.query empty |
| Date: | 2022-04-26 13:59:14 |
| Message-ID: | CAKFQuwbGGMETbFKV7BwW95Hr0OK2HeWpdTA6m=KhpeEbugfSUg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 26, 2022 at 6:55 AM Robert Lichtenberger <
r(dot)lichtenberger(at)synedra(dot)com> wrote:
> When executing "SELECT * FROM pg_stat_activity" I get lots of rows that
> have an empty "query" column.
>
> According to [1] this column should contain the "Text of this backend's
> most recent query", either a query that is currently running or the last
> query that was executed.
>
> So how comes that a lot of the rows in pg_stat_activity have an empty
> "query"?
>
>
>
> https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-PG-STAT-ACTIVITY-VIEW
>
>
They've never executed a query. Probably due to connection pooling opening
connections for the pool but never needing to hand them out.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2022-04-26 14:24:12 | Re: pg_stat_activity.query empty |
| Previous Message | Robert Lichtenberger | 2022-04-26 13:55:25 | pg_stat_activity.query empty |