pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mike White <mikewhite22@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres 7.4 VACUUM FULL multiple AccessExclusiveLocks?
Date: Fri, 04 Jan 2008 14:18:03 -0500
Message-ID: <20971.1199474283@sss.pgh.pa.us> (raw)
In-Reply-To: <715193.26887.qm@web34711.mail.mud.yahoo.com>
References: <715193.26887.qm@web34711.mail.mud.yahoo.com>

Mike White <mikewhite22@yahoo.com> 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



view thread (3+ messages)

Message-ID: <20971.1199474283@sss.pgh.pa.us>
Permalink:  ../20971.1199474283@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/20971.1199474283@sss.pgh.pa.us

 · 

reply

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, mikewhite22@yahoo.com
  Subject: Re: Postgres 7.4 VACUUM FULL multiple AccessExclusiveLocks?
  In-Reply-To: <20971.1199474283@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