Re: vacuum deadlock

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Ibrahim Harrani <ibrahim(dot)harrani(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: vacuum deadlock
Date: 2010-02-06 06:11:36
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-admin

Ibrahim Harrani <ibrahim(dot)harrani(at)gmail(dot)com> writes:
> I got a deadlock while vacuuming all databases with vacuumdb command.

> vacuumdb: vacuuming of database "mydb" failed: ERROR: deadlock detected
> DETAIL: Process 1294 waits for AccessExclusiveLock on relation 2662 of
> database ; blocked by process 1807.
> Process 1807 waits for AccessShareLock on relation 1259 of database 16389;
> blocked by process 1294.

vacuumdb -f you mean? An ordinary vacuum wouldn't be trying to take

It might be that you have an instance of a failure that was identified
just a couple weeks ago:

regards, tom lane

In response to


Browse pgsql-admin by date

  From Date Subject
Next Message Kiswono Prayogo 2010-02-08 03:22:12 Best Replication Tool
Previous Message Josh Kupershmidt 2010-02-05 22:55:33 [patch] pg_cancel_backend for unprivileged users