easy task: concurrent select-updates

From: Nickolay <nitro(at)zhukcity(dot)ru>
To: pgsql-general(at)postgresql(dot)org
Subject: easy task: concurrent select-updates
Date: 2009-09-03 08:05:47
Message-ID: 4A9F78DB.6070204@zhukcity.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi All,

I have a trivial task. There is a table with messages queue, let's say
"msg_queue".
There are a few processes and each of them is taking one message from
this table at a time to transmit into communication channel.
I've done it my way, but I have postgresql's messages about deadlocks
and a lot of warnings.

I my program, every process is doing approx the following procedure:
SELECT ... FROM msg_queue WHERE busy = false ORDER BY ... LIMIT 1;
if a message was found:
BEGIN;
SELECT id FROM msg_queue WHERE id = ... AND busy = false FOR SHARE;
UPDATE msg_queue SET busy = true, channel_id = ... WHERE id = ... AND
busy = false;
COMMIT;

I do understand that this way is stupid, but I have not came with
anything else yet.
Could somebody share ideas how to do this so the same message 100% WOULD
NOT be transmitted over two or more channels.
Sorry for the newbie question!

Best regards, Nick.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nickolay 2009-09-03 08:09:15 Re: easy task: concurrent select-updates
Previous Message Allan Kamau 2009-09-03 07:44:04 Does PG cache results of an aggregate function, (and results of non-volatile functions)?