From: | "Porwal, Utkarsh" <utkarsh(dot)porwal(at)emc(dot)com> |
---|---|
To: | "Porwal, Utkarsh" <utkarsh(dot)porwal(at)emc(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Query on Postgres locks |
Date: | 2015-09-24 09:37:45 |
Message-ID: | 182E8934F4D0094A94B8A0E5A48B8F5A35609F81@MX105CL01.corp.emc.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
The postgres version is –
psql (9.0.7)
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Porwal, Utkarsh
Sent: Thursday, September 24, 2015 3:04 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] Query on Postgres locks
Dear All,
I have a perl script which will attempt to drop/recreate some intermediate tables. This works by trying to acquire an access exclusive lock on the intermediate tables.
When there is a backup running through pg_dump, I see an entry in pg_locks/pg_stat_activity table for the above which is waiting for pg_dump to finish, which is expected.
Since backup on huge environment takes around 8 hrs to complete, I noticed that the entries waiting for locks are removed after certain amount of time which I couldn’t record even though the perl script is still running.
Do you guys know if the lock waiting will ultimately timeout and when? I don’t have any statement_timeout specified.
Any pointers on this behavior?
Regards,
Utkarsh
From | Date | Subject | |
---|---|---|---|
Next Message | Wei Shan | 2015-09-24 10:19:28 | Re: Query on Postgres locks |
Previous Message | Porwal, Utkarsh | 2015-09-24 09:34:10 | Query on Postgres locks |