Re: Clustering with minimal locking
| От | Gurjeet Singh |
|---|---|
| Тема | Re: Clustering with minimal locking |
| Дата | |
| Msg-id | 65937bea0806180109m68bdb53cke3c74077f32d59ee@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Clustering with minimal locking (Decibel! <decibel@decibel.org>) |
| Список | pgsql-general |
On Wed, Jun 18, 2008 at 9:26 AM, Decibel! <decibel@decibel.org> wrote:
Really!!? Am I missing something? How can a single transaction, running synchronous commands, deadlock itself!
Best regards,
--
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
Mail sent from my BlackLaptop device
On Jun 17, 2008, at 11:37 AM, Scott Ribe wrote:Actually, no (at least in 8.2). CLUSTER grabs an exclusive lock before it does any work meaning that it can't deadlock by itself. Of course you could always do something likeBOOM! Deadlock.
No more likely than with the current cluster command. Acquiring the lock is
the same risk; but it is held for much less time.
BEGIN;
SELECT * FROM a;
CLUSTER .. ON a;
COMMIT;
Which does introduce the risk of a deadlock
Really!!? Am I missing something? How can a single transaction, running synchronous commands, deadlock itself!
Best regards,
gurjeet[.singh]@EnterpriseDB.com
singh.gurjeet@{ gmail | hotmail | indiatimes | yahoo }.com
EnterpriseDB http://www.enterprisedb.com
Mail sent from my BlackLaptop device
В списке pgsql-general по дате отправления: