The Curious Case of the Table-Locking UPDATE Query - Mailing list pgsql-general

From Emiliano Saenz
Subject The Curious Case of the Table-Locking UPDATE Query
Date
Msg-id CAMdU7qsXphcRDKc33QuvVwmymH1HaahJTatgA32+2So_h7m4OA@mail.gmail.com
Whole thread Raw
Responses Re: The Curious Case of the Table-Locking UPDATE Query  (Adrian Klaver <adrian.klaver@aklaver.com>)
Re: The Curious Case of the Table-Locking UPDATE Query  (hubert depesz lubaczewski <depesz@depesz.com>)
List pgsql-general
Hello!
We have a huge POSTGRES 9.4 database in the production environment (several tables have more than 100.000.00 registers). Last two months we have had problems with CPU utilization. Debugging the locks (on pg_locks) we notice that sometimes simple UPDATE (by primary key) operation takes out ACCESS_EXCLUSIVE_LOCK mode over these huge tables so POSTGRES DB collapses and it generates excessive CPU consumption. My question is, How is it possible that UPDATE operation takes out ACCESS_EXCLUSIVE_LOCK mode?
More information, this system never manifests this behavior before and we don't make software changes on last 2 years
Attachment

pgsql-general by date:

Previous
From: Vijaykumar Jain
Date:
Subject: Re: Logical Replication - Single Destination Table With Multiple Source Tables - How to Handle Structure Changes
Next
From: Adrian Klaver
Date:
Subject: Re: The Curious Case of the Table-Locking UPDATE Query