Re: pg_stat_activity

From: pavan95 <pavan(dot)postgresdba(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: pg_stat_activity
Date: 2018-06-12 08:03:40
Message-ID: 1528790620675-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi David,

On Monday, June 11, 2018, pavan95 <[hidden email]> wrote:
Hi David,

>>You can also configure table level audit with the help of triggers to
capture DML's

​>How?

Please find below procedure to configure table level audit with the help of
triggers :
[...]

That's it and you are done. Just add the table you want to track the DML's
in the below way:

>I'm missing the part where any of that has to do with pg_stat_activity and
the question that this >thread is about...in particular the part about
select statements.

Yeah, this method is to track the execution times of the DML queries(long
running), just said if Ron's intention was to identify the long running
queries might be SELECT .. FOR UPDATES, he can use this method.
And it is not related in any way with pg_stat_activity.

Regards,
Pavan

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Pierre Ochsenbein 2018-06-12 14:38:41 pg_restore failed with the extension uuid-ossp.control
Previous Message Thomas Kellerer 2018-06-12 07:42:06 Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix