From: Tom Lane <tgl@sss.pgh.pa.us>
To: Denis Khabas <dkhabas@bluecatnetworks.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Which SQL command creates ExclusiveLock?
Date: Wed, 28 Apr 2004 00:16:28 -0400
Message-ID: <22918.1083125788@sss.pgh.pa.us> (raw)
In-Reply-To: <5DEC3FFCDE2F7C4DA45433EE09A4F22C013457FF@colossus.dyadem.corp>
References: <5DEC3FFCDE2F7C4DA45433EE09A4F22C013457FF@colossus.dyadem.corp>
"Denis Khabas" <dkhabas@bluecatnetworks.com> writes:
> According to postgres documentation, all update operations place ROW EXCLUS=
> IVE MODE locks, and=20
> EXCLUSIVE MODE is not automatically acquired by any postgres SQL command. S=
> o, which command places
> ExclusiveLock?
It says that no SQL command acquires ExclusiveLock *on a table*. The
pg_locks row you show represents ExclusiveLock on a transaction number.
Every transaction gets ExclusiveLock on its transaction number for the
duration of its existence.
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, dkhabas@bluecatnetworks.com
Subject: Re: Which SQL command creates ExclusiveLock?
In-Reply-To: <22918.1083125788@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