Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1u9R-0001GH-1a for pgsql-admin@arkaria.postgresql.org; Thu, 07 Mar 2019 14:37:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h1u9P-0001py-My for pgsql-admin@arkaria.postgresql.org; Thu, 07 Mar 2019 14:37:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1h1u9P-0001pr-FZ for pgsql-admin@lists.postgresql.org; Thu, 07 Mar 2019 14:37:35 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1h1u9J-00009i-7k for pgsql-admin@postgresql.org; Thu, 07 Mar 2019 14:37:35 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id E98A6126EBE9B for ; Thu, 7 Mar 2019 07:37:26 -0700 (MST) Date: Thu, 7 Mar 2019 07:37:26 -0700 (MST) From: pavan95 To: pgsql-admin@postgresql.org Message-ID: <1551969446954-0.post@n3.nabble.com> Subject: Re: Too many Row Exclusive Locks held for a long time MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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