Re: pg_stat_activity - Mailing list pgsql-admin

From Pavan Teja
Subject Re: pg_stat_activity
Date
Msg-id CACh9nsZBYxBrgfFtK-KPB4x-8vZi83Sx=Qzbgf4cpVg+M2SDJA@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_activity  (Rui DeSousa <rui.desousa@icloud.com>)
Responses Re: pg_stat_activity  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-admin


On Mon, Jun 11, 2018, 9:58 PM Rui DeSousa <rui.desousa@icloud.com> wrote:

> On Jun 11, 2018, at 9:56 AM, Ron <ronljohnsonjr@gmail.com> wrote:
>
> How, then, do I get only long-running SELECT statements?
>

Why only select statements? What about select statements that are really updates?

i.e.

select …. for update;
select do_some_work();   —In this case you will not see the actual executing SQL in the function which could be update, delete, select, etc.

Or what about delete or update with returning?

Hi Ron,

You can use LIKE  operator for getting updates and deletes and inserts like 

" Select * from pg_stat_activity where query like '%UPDATE%' or '%update%' "

The same in case of updates and deletes.  You can also configure table level audit with the help of triggers to capture DML's 


Hope this helps.

Thanks & Regards,
Pavan.


pgsql-admin by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_stat_activity