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
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

Browse pgsql-hackers by date

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