Re: pg_stat_activity

From: Rui DeSousa <rui(dot)desousa(at)icloud(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 16:27:56
Message-ID: BC0EBD96-110B-4CC7-A5B3-3088C40EEDA7@icloud.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


> On Jun 11, 2018, at 9:56 AM, Ron <ronljohnsonjr(at)gmail(dot)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?

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Rui DeSousa 2018-06-11 16:52:49 Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix
Previous Message Ron 2018-06-11 16:12:28 Re: pg_stat_activity