←back to thread

Locks in PostgreSQL: 3. Other locks (2020)

(habr.com)
60 points fanf2 | 1 comments | 07 Dec 25 15:42 UTC | HN request time: 0.282s | source
Show context
semiquaver ◴[07 Dec 25 16:06 UTC] No.46182699[source]▶
Don’t skip the discussion on advisory locks. In my experience nearly every nontrivial application that spans multiple machines has concurrency bugs that advisory locks are perfectly suited to fix.
replies(4): >>46183073 #>>46183165 #>>46183758 #>>46183971 #
1. GeertJohan ◴[07 Dec 25 17:05 UTC] No.46183165[source]▶
They are great, although I wouldnt use the articles advice on using hashtext to get a number for the lock. This may cause collisions, especially when used with a large number of locks.

In a project Im working on we have a single go package that holds a list of all advisory lock numbers as constants.