17 ms·

Seems like if you tried to use transactions, you'd have the same problem?

• karmakaze 7y ago
  A transaction executes all commands using the same connection so it would have worked. The semantics are different though where the commands issued between the lock and unlock aren't atomic if issued on the same connection but not in a tx.
• AlfeG 7y ago
  For transactions You should use different advisory lock tied to transaction: pg_advisory_xact_lock. This should solve problem even for sessions reuse and connection pooling