Re: Serialized Transaction Locking Issues

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: justin <jtyme(at)intrusic(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Serialized Transaction Locking Issues
Date: 2003-02-04 23:21:28
Message-ID: 18900.1044400888@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

justin <jtyme(at)intrusic(dot)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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Luke Pascoe 2003-02-05 03:39:09 Inserting a tab character
Previous Message Jan Wieck 2003-02-04 23:14:02 Re: iceberg queries