https://www.postgresscripts.com/tags/concurrency/Recent content in Concurrency on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comMon, 08 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/postgresql-advisory-locks-with-pg-advisory-lock/Mon, 08 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/postgresql-advisory-locks-with-pg-advisory-lock/ <h2 id="postgresql-advisory-locks-with-pg_advisory_lock">PostgreSQL Advisory Locks with pg_advisory_lock</h2> <p>Two scheduled jobs fire at the same minute and both try to process the same nightly batch. Nothing in the data stops them — there is no single row to lock, because the work has not produced rows yet. Row and table locks are the wrong tool here. What you want is a named lock that the application agrees to respect, held for as long as the job runs. PostgreSQL provides this with advisory locks through <code>pg_advisory_lock</code> and its companion functions.</p>