Csaba Nagy wrote: > On Wed, 2008-07-09 at 16:23 +0800, Craig Ringer wrote: >> Especially if it returned an updated row count or supported the >> RETURNING clause, so you could find out after the fact what was or >> wasn't done. > > Well, it is supposed to be used as "SELECT ... FOR UPDATE SKIP LOCKED", > so you can in fact put the locked row ids in the target list. With a > "LIMIT 1" appended would be the perfect way to check out the next queue > item to process...
That makes sense. I was thinking of UPDATE ... SKIP LOCKED RETURNING instead, which could be handy in similar situations. -- Craig Ringer -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
