| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_activity |
| Date: | 2018-06-12 05:58:14 |
| Message-ID: | CAKFQuwZGZzbVKjhznx6pY+NXGvNCD2Oytz0Fma53ZbCnZVQagg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Monday, June 11, 2018, pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> 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.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | pavan95 | 2018-06-12 06:09:55 | Re: PostgreSQL 'Corruption & Fragmentation' detection and resolution/fix |
| Previous Message | pavan95 | 2018-06-12 05:31:49 | Re: pg_stat_activity |