| From: | Craig Jackson <craig(dot)jackson(at)broadcom(dot)com> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Table/log file name which store the queries which got executed in last 1 month |
| Date: | 2020-05-04 15:36:42 |
| Message-ID: | CA+R1LV4vGSqh345SWCgzpMXt8qXjGTSt5dVnZA3wRee2nzZSjw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Going forward you might consider enabling the parameter
track_commit_timestamp
This would allow you to view the latest transaction commit times for rows
in a table, but be aware that there will be some performance overhead by
enabling this.
Regards,
Craig
On Fri, May 1, 2020 at 1:55 AM legrand legrand <legrand_legrand(at)hotmail(dot)com>
wrote:
> If thoses users are connected with distinct accounts from application into
> the database, maybe that pg_stat_statements may help see
> https://www.postgresql.org/docs/current/pgstatstatements.html
>
> Regards
> PAscal
>
>
>
>
> --
> Sent from: https://www.postgresql-archive.org/PostgreSQL-sql-f2142323.html
>
>
>
--
Craig
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ertan.kucukoglu | 2020-05-11 21:17:27 | Exporting modifications to a table as XML/JSON |
| Previous Message | David G. Johnston | 2020-05-02 01:24:53 | Re: pg_dump fails when a table is in ACCESS SHARE MODE |