Date: Tue, 12 Jun 2018 01:03:40 -0700 (MST)
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1528790620675-0.post@n3.nabble.com>
In-Reply-To: 
 <CAKFQuwZGZzbVKjhznx6pY+NXGvNCD2Oytz0Fma53ZbCnZVQagg@mail.gmail.com>
References: <4405957b-2e0f-bfc5-eaf6-5e2864da2796@gmail.com>
 <CAGDYbUM0Lv-fcFp_Mh4jyBtSrW24Z1psvey6FBi5q=LQx=7CMQ@mail.gmail.com>
 <9884a24a-c129-a1a9-1901-2a9c8987331e@gmail.com>
 <BC0EBD96-110B-4CC7-A5B3-3088C40EEDA7@icloud.com>
 <CACh9nsZBYxBrgfFtK-KPB4x-8vZi83Sx=Qzbgf4cpVg+M2SDJA@mail.gmail.com>
 <CAKFQuwYx=uBJ+=Vn_WuQ81HX0mFrXMLg36xN9vHFohH+U2uYAQ@mail.gmail.com>
 <1528781509107-0.post@n3.nabble.com>
 <CAKFQuwZGZzbVKjhznx6pY+NXGvNCD2Oytz0Fma53ZbCnZVQagg@mail.gmail.com>
Subject: Re: pg_stat_activity
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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=20

=E2=80=8B>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.=20
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