Re: Processing a work queue - Mailing list pgsql-general

From John D. Burger
Subject Re: Processing a work queue
Date
Msg-id 02E41FE2-7896-478A-8ED7-0BEDCFC0E940@mitre.org
Whole thread Raw
In response to Re: Processing a work queue  ("John D. Burger" <john@mitre.org>)
Responses Re: Processing a work queue  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I wrote:

> I use a variant of The Tom Lane Solution previously pointed to,
> your Plan 1 is very similar.

Hmm, per that pointed-to post:

   http://archives.postgresql.org/pgsql-general/2003-05/msg00351.php

I decided to run a periodic vacuum on my work queue.  Lo and behold,
I get this:

   ERROR:  tuple concurrently updated

In addition, all of my workers locked up, apparently indefinitely.  I
presume this was because I was foolishly doing VACUUM FULL, which
locks the table.  But what exactly was going on?  Why did my workers
hang?  Thanks in advance, I am new to all this concurrency stuff ...

- John Burger
   MITRE

pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Preferred Installation/Data Directories
Next
From: Tom Lane
Date:
Subject: Re: Processing a work queue