Re: pg_stat_activity - Mailing list pgsql-admin

From David G. Johnston
Subject Re: pg_stat_activity
Date
Msg-id CAKFQuwZnt_CjE+xipRpS95vWWAmuaOVDm2A=4UuO+1kZGnXhkA@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_activity  (Ron <ronljohnsonjr@gmail.com>)
Responses Re: pg_stat_activity  (Ron <ronljohnsonjr@gmail.com>)
List pgsql-admin
On Mon, Jun 11, 2018 at 8:07 AM, Ron <ronljohnsonjr@gmail.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.

pgsql-admin by date:

Previous
From: Pierre Ochsenbein
Date:
Subject: Add to watchdog cluster request is rejected by node
Next
From: Ron
Date:
Subject: Re: pg_stat_activity