From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ibrahim Harrani <ibrahim.harrani@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: vacuum deadlock
Date: Sat, 06 Feb 2010 01:11:36 -0500
Message-ID: <14784.1265436696@sss.pgh.pa.us> (raw)
In-Reply-To: <530068a1002050143n26ee05c6hda0de69f5ed97a9d@mail.gmail.com>
References: <530068a1002050143n26ee05c6hda0de69f5ed97a9d@mail.gmail.com>
Ibrahim Harrani <ibrahim.harrani@gmail.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
AccessExclusiveLock.
It might be that you have an instance of a failure that was identified
just a couple weeks ago:
http://archives.postgresql.org/pgsql-committers/2010-01/msg00199.php
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ibrahim.harrani@gmail.com
Subject: Re: vacuum deadlock
In-Reply-To: <14784.1265436696@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox