| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, 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 14:24:12 |
| Message-ID: | b0c734cdbd70b890cc719bdc5ab2b4512a02f522.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, 2022-04-26 at 06:59 -0700, David G. Johnston wrote:
> 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.
An alternative option is that the last query sent was an empty string.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2022-04-26 14:47:19 | Re: pg_stat_activity.query empty |
| Previous Message | David G. Johnston | 2022-04-26 13:59:14 | Re: pg_stat_activity.query empty |