Re: Too many Row Exclusive Locks held for a long time

From: pavan95 <pavan(dot)postgresdba(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Too many Row Exclusive Locks held for a long time
Date: 2019-03-07 14:37:26
Message-ID: 1551969446954-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Community,

Hope my mail finds you in fine time.

I am facing an issue in one of the production servers.

I have been observing there are many "Row Exclusive" locks occurring on a
set of similar tables around 2000 locks at any given point of time. And
then the application(Odoo) is being struck for a very long time.

After we kill those Row Exclusive locks all the locks were released.

Typically the below is the sample statement being run on database by the
application users:

SELECT id FROM abc WHERE id=5075 FOR UPDATE NOWAIT;

So every time this issue occurs we need to go into server identify the "Row
Exclusive Locks" process id's and kill them after which it works fine.

So is there any permanent fix for this that we need to look upon?

Kindly shed some light on this area.

Thanks in Advance. Looking forward to hear from you.

Regards,
Pavan Teja,
9841380956

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Andrew Gierth 2019-03-07 17:20:42 Re: Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible
Previous Message Peter 2019-03-07 14:04:21 Upgrade 10.5->10.6 : db crash BUS ERROR (sig 10), reproducible