DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=message-id:date:from:user-agent:mime-version:to:cc:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	b=u+02vXhaR8jXhOqt55oaR8LfSE4KeMlhyTpEw6eGS++75s2A0oSo7AZf/FW23wevNl
	NpjmzAv6D+sH1uxIwKHukY7c47Bp9yzKerO04MKsEuCxK51DlEgB9GrVjjQl20kT7CHx
	qVXDQLPQgiy2NUYpWUSnAGzIUkyA5PNRBA2dQ=
Message-ID: <4B6C10BA.8050003@gmail.com>
Date: Fri, 05 Feb 2010 13:36:10 +0100
From: Yeb Havinga <yebhavinga@gmail.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Ibrahim Harrani <ibrahim.harrani@gmail.com>
CC: pgsql-admin@postgresql.org
Subject: Re: vacuum deadlock
References: <530068a1002050143n26ee05c6hda0de69f5ed97a9d@mail.gmail.com>
In-Reply-To: <530068a1002050143n26ee05c6hda0de69f5ed97a9d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Ibrahim Harrani wrote:
> Hi,
>
> I am using PostgreSQL 8.3.7.
> autovacuum is enabled in postgresql.conf
>
> 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.
>
> I think, because of this lock, deleting a large table (15 million 
> records) was taking too much time
> How can I know the name of the relations 2662 and 1259?
postgres=# select oid,relname from pg_class where oid in (2662,1259);
 oid  |      relname      
------+--------------------
 2662 | pg_class_oid_index
 1259 | pg_class
(2 rows)
> Do you have any ide about the problem and solution?
It would be interesting to know what are the processes 1807 and 1294. 
Once that is known, try to avoid executing both processes concurrently.

regards
Yeb Havinga