From 080855660c2e7d6fff9b0b98f92be29bc278bb00 Mon Sep 17 00:00:00 2001 From: Gibheer Date: Wed, 16 Dec 2015 16:49:48 +0100 Subject: [PATCH] this is not a draft anymore --- content/post/121.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/post/121.md b/content/post/121.md index 3e09ad9..27a1797 100644 --- a/content/post/121.md +++ b/content/post/121.md @@ -2,7 +2,7 @@ title = "fast application locks" date = "2015-12-16T16:15:44+00:00" author = "Gibheer" -draft = true +draft = false +++ This week I was looking for a mechanism to build an application specific lock in postgres. I did know about `pg_try_advisory_lock(long)` and `pg_try_advisory_lock(int, int)`, but could not figure out a good mechanism until I found depesz blog entry about [how to pick a task of a list](http://www.depesz.com/2013/08/30/pick-a-task-to-work-on/).