Skip site navigation (1) Skip section navigation (2)

Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Scher <js(at)oxado(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock?
Date: 2007-03-01 15:31:38
Message-ID: 24391.1172763098@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Jonathan Scher <js(at)oxado(dot)com> writes:
> CLUSTER uses an ACCESS EXCLUSIVE lock. Why does it forbid concurrent reads?

Because when it drops the old copy of the table there had better not be
any concurrent readers.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Zeugswetter Andreas ADI SDDate: 2007-03-01 15:43:01
Subject: Re: HOT - preliminary results
Previous:From: Jim C. NasbyDate: 2007-03-01 15:24:22
Subject: Re: COMMIT NOWAIT Performance Option

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group