Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 660A82E3986 for ; Fri, 4 Jan 2008 15:18:09 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 48265-08-2 for ; Fri, 4 Jan 2008 15:18:02 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 46E772E3347 for ; Fri, 4 Jan 2008 15:18:04 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id m04JI3Hj020972; Fri, 4 Jan 2008 14:18:03 -0500 (EST) To: Mike White cc: pgsql-admin@postgresql.org Subject: Re: Postgres 7.4 VACUUM FULL multiple AccessExclusiveLocks? In-reply-to: <715193.26887.qm@web34711.mail.mud.yahoo.com> References: <715193.26887.qm@web34711.mail.mud.yahoo.com> Comments: In-reply-to Mike White message dated "Thu, 03 Jan 2008 15:12:37 -0800" Date: Fri, 04 Jan 2008 14:18:03 -0500 Message-ID: <20971.1199474283@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/69 X-Sequence-Number: 27843 Mike White writes: > I've noticed that the pg_lock table shows two AccessExclusiveLock > entries that are completely identical. Is this a sign of internal > deadlock, or is this behavior expected during VACUUM FULL operation? I think it's just the regular and session versions of the lock. Don't recall at the moment whether it's easier to tell them apart in newer releases. > Also, please don't tell me to upgrade. You should *definitely* be on 7.4.x where x is considerably greater than 7. This is a painless update and failing to do it borders on negligence. Read the release notes at http://www.postgresql.org/docs/7.4/static/release.html regards, tom lane