Re: Processing a work queue

From: "John D(dot) Burger" <john(at)mitre(dot)org>
To: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Processing a work queue
Date: 2007-04-27 17:06:42
Message-ID: 02E41FE2-7896-478A-8ED7-0BEDCFC0E940@mitre.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-04-27 17:18:38 Re: Processing a work queue
Previous Message Jim Nasby 2007-04-27 16:12:21 Re: Feature Request --- was: PostgreSQL Performance Tuning