single-row deadlock

Started by Nonamealmost 5 years ago2 messagesgeneral

guntiso@latnet.lv

almost 5 years ago

Hi,

After upgrading from PostgreSQL 9.6 to 13 we started to experience
locking issues once per week or two.
Replacing exclusive table lock with helper table row lock did not help.
Now it seems like a single-row deadlocks can occur, which should not be
possible (audit_data_lock table contains one row):

blocked_pid,blocking_pid,blocked_statement,current_statement_in_blocking_process,blocked_application,blocking_application
6752,6577,update audit_data_lock set locks_used = locks_used + 1,update
audit_data_lock set locks_used = locks_used + 1,PostgreSQL JDBC
Driver,PostgreSQL JDBC Driver
6577,6752,update audit_data_lock set locks_used = locks_used + 1,update
audit_data_lock set locks_used = locks_used + 1,PostgreSQL JDBC
Driver,PostgreSQL JDBC Driver

Is this a known issue? It seems like
https://postgrespro.com/list/thread-id/1231581. Are there any
workarounds?

Noname

guntiso@latnet.lv

over 4 years ago

In reply to: Noname (#1)

Re: single-row deadlock

After upgrading from PostgreSQL 9.6 to 13 we started to experience
locking issues once per week or two.

This turned out to be a performance problem and reused pid-s. No
deadlock.