From: Tom Lane <tgl@sss.pgh.pa.us>
To: emil@baymountain.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Exclusive lock question
Date: Wed, 29 Jun 2005 11:27:47 -0400
Message-ID: <9798.1120058867@sss.pgh.pa.us> (raw)
In-Reply-To: <200506291108.28516.emil@baymountain.com>
References: <200506291108.28516.emil@baymountain.com>
Emil Briggs <emil@baymountain.com> writes:
> When I see the slowdowns there are hundreds of these with no entry for
> relation or database. Any ideas what is being locked in this case?
Per the pg_locks documentation:
Every transaction holds an exclusive lock on its transaction ID for its
entire duration. If one transaction finds it necessary to wait
specifically for another transaction, it does so by attempting to
acquire share lock on the other transaction ID. That will succeed only
when the other transaction terminates and releases its locks.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, emil@baymountain.com
Subject: Re: Exclusive lock question
In-Reply-To: <9798.1120058867@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