| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Siraj G <tosiraj(dot)g(at)gmail(dot)com>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Finding detailed information about LOCKS |
| Date: | 2024-05-03 06:16:17 |
| Message-ID: | 0410bdf03cad96a0fec82b9a8c49e05ab5a79b51.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, 2024-05-03 at 10:54 +0530, Siraj G wrote:
> I come from Oracle background. In Oracle there is a licensed feature (Diagnostics + Tuning)
> upon using which the system keeps historic session records, which gives a better way
> to find out locking related details- like the blocking session, total sessions blocked
> and the time the blocking event was active. I am finding it a little hard in PgSQL
> to find this information.
>
> I am seeking help in finding a detailed analysis on the locks that happened yesterday,
> 2 days back or in the last week. Can someone assist please.
PostgreSQL doesn't keep historical information on these things.
You need a monitoring tool like pgwatch2 that takes regular snapshots of these data
and allows you to access this information.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wasim Devale | 2024-05-03 06:22:00 | Re: Finding detailed information about LOCKS |
| Previous Message | Siraj G | 2024-05-03 05:24:38 | Finding detailed information about LOCKS |