| 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 18:01:21 |
| Message-ID: | 80033C9D-DCA8-4BDB-BDA3-9FD0EFA8E2DB@mitre.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>> I decided to run a periodic vacuum on my work queue. Lo and behold,
>> I get this:
>
>> ERROR: tuple concurrently updated
>
> Which PG version is this, and do you have autovacuum enabled?
7.4.8, so no autovac, right?
>> In addition, all of my workers locked up, apparently indefinitely.
>
> [ squint... ] That shouldn't happen. Look into pg_locks to see if
> you can determine who's waiting for what.
I don't want to recreate the problem right now, but I will
investigate later. For what it's worth, while the workers were
locked up, I couldn't query the table in psql either.
- John D. Burger
MITRE
| From | Date | Subject | |
|---|---|---|---|
| Next Message | RPK | 2007-04-27 18:09:49 | Store dates in database in different format |
| Previous Message | Josh Berkus | 2007-04-27 17:59:49 | Re: Feature Request --- was: PostgreSQL Performance Tuning |