Re: BDR - DDL Locking
От | Craig Ringer |
---|---|
Тема | Re: BDR - DDL Locking |
Дата | |
Msg-id | CAMsr+YGNO-NtJ76DdO0S0yopM_XBj66g1JD29BdZyGUCmz67BA@mail.gmail.com обсуждение исходный текст |
Ответ на | BDR - DDL Locking (Will McCormick <wmccormick@gmail.com>) |
Ответы |
Re: BDR - DDL Locking
|
Список | pgsql-general |
What's the *exact* BDR version? When you say you "attempted to" - what was the outcome? Presumably an ERROR from the TRUNCATE, right? That would roll back the transaction, and in the process abort the DDL lock acquisition attempt. Are you sure replication was working normally prior to this point, with no issues? The global DDL lock isn't a true lock in the sense that it appears in pg_locks, etc. If you roll back the transaction trying to acquire it, or terminate the PostgreSQL backend attempting to acquire it - such as your TRUNCATE - using pg_terminate_backend(...) then it will be removed automatically. If for any reason that is not the case (which it shouldn't be) then restarting the nodes will clear it.
В списке pgsql-general по дате отправления: