From: Tom Lane <tgl@sss.pgh.pa.us>
To: justin <jtyme@intrusic.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Serialized Transaction Locking Issues
Date: Tue, 04 Feb 2003 18:21:28 -0500
Message-ID: <18900.1044400888@sss.pgh.pa.us> (raw)
In-Reply-To: <3E403A3E.5020508@intrusic.com>
References: <3E403A3E.5020508@intrusic.com>
justin <jtyme@intrusic.com> writes:
> I'm currently in the midst of working on a serializable transaction
> which drops indexes on several tables, does a bulk copy, and rebuilds
> the indexes. Based on what I've read it seemed as though I'd be able to
> concurrently execute read only queries against these tables,
Nope, because "drop index" obtains an exclusive lock on the table.
(If it didn't, some other query might try to *use* the index, which
would create a bit of a problem if the DROP committed midway through.)
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, jtyme@intrusic.com
Subject: Re: Serialized Transaction Locking Issues
In-Reply-To: <18900.1044400888@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