Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock?
Date
Msg-id 24391.1172763098@sss.pgh.pa.us
Whole thread Raw
In response to CLUSTER, using SHARE UPDATE EXCLUSIVE lock?  (Jonathan Scher <js@oxado.com>)
Responses Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock?  (Jonathan Scher <js@oxado.com>)
List pgsql-hackers
Jonathan Scher <js@oxado.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


pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: COMMIT NOWAIT Performance Option
Next
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: HOT - preliminary results