CLUSTER, using SHARE UPDATE EXCLUSIVE lock?

Поиск
Список
Период
Сортировка
От Jonathan Scher
Тема CLUSTER, using SHARE UPDATE EXCLUSIVE lock?
Дата
Msg-id 45E6DB57.6000107@oxado.com
обсуждение исходный текст
Ответы Re: CLUSTER, using SHARE UPDATE EXCLUSIVE lock?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
Hello,

CLUSTER uses an ACCESS EXCLUSIVE lock. Why does it forbid concurrent reads?
Florian G. Pflug, on a post ( 
http://archives.postgresql.org/pgsql-hackers/2007-02/msg00081.php ) 
suggested that there were no way to let the old entry until the command 
commit.
I would like Cluster to create a new table, copying old values to this 
one, then delete the old one. This would allow Cluster to work with a 
share update exlusive lock, in order to allow reading the table while 
cluster is working.

How does Cluster actually works? Why making a Cluster command less 
restrictive isn't even in the TO-list?

Best regards,
Jonathan Scher


В списке pgsql-hackers по дате отправления:

Предыдущее
От: "Simon Riggs"
Дата:
Сообщение: Re: [PATCHES] WIP Patch - Updateable Cursors
Следующее
От: "Florian G. Pflug"
Дата:
Сообщение: Updated propsoal for read-only queries on PITR slaves (SoC 2007)