Skip site navigation (1) Skip section navigation (2)

Deadlock in vacuum (check fails)

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Deadlock in vacuum (check fails)
Date: 2010-01-13 10:11:27
Message-ID: 4B4D9C4F.1030604@sun.com (view raw or flat)
Thread:
Lists: pgsql-hackers
I found following strange error on gothic moth:


================== pgsql.22658/src/test/regress/regression.diffs 
===================
*** 
/zfs_data/home/postgres/buildfarm/gothic_moth/HEAD/pgsql.22658/src/test/regress/expected/vacuum.out 
Tue Jan 12 22:06:13 2010
--- 
/zfs_data/home/postgres/buildfarm/gothic_moth/HEAD/pgsql.22658/src/test/regress/results/vacuum.out 
Tue Jan 12 22:35:25 2010
***************
*** 94,99 ****
--- 94,103 ----
   -- only non-system tables should be changed
   VACUUM FULL pg_am;
   VACUUM FULL pg_class;
+ ERROR:  deadlock detected
+ DETAIL:  Process 5913 waits for AccessExclusiveLock on relation 2662 
of database 16384; blocked by process 5915.
+ Process 5915 waits for AccessShareLock on relation 1259 of database 
16384; blocked by process 5913.
+ HINT:  See server log for query details.
   VACUUM FULL pg_database;
   VACUUM FULL vaccluster;
   VACUUM FULL vacid;


Detail here:

http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=gothic_moth&dt=2010-01-12%2021:06:01

	Zdenek

Responses

pgsql-hackers by date

Next:From: Heikki LinnakangasDate: 2010-01-13 10:27:10
Subject: Re: Streaming replication and non-blocking I/O
Previous:From: Boszormenyi ZoltanDate: 2010-01-13 09:14:12
Subject: Re: lock_timeout GUC patch

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group