Re: pg_stat_activity

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Ron <ronljohnsonjr(at)gmail(dot)com>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_stat_activity
Date: 2018-06-11 15:21:56
Message-ID: CAKFQuwZnt_CjE+xipRpS95vWWAmuaOVDm2A=4UuO+1kZGnXhkA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Jun 11, 2018 at 8:07 AM, Ron <ronljohnsonjr(at)gmail(dot)com> wrote:

> That won't work, because that would catch any query on a table which
> happens to have the string "select" in a table, index or column name.
>

​I don't believe what you are asking is possible using only
pg_stat_activity. One thought that comes to mind is to identify, via
pg_locks, sessions that hold non-read-only locks and then exclude the rows
in pg_stat_activity that match up with those sessions.

David J.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2018-06-11 16:12:28 Re: pg_stat_activity
Previous Message Pierre Ochsenbein 2018-06-11 15:12:00 Add to watchdog cluster request is rejected by node