Re: BDR - DDL Locking - Mailing list pgsql-general

From Craig Ringer
Subject Re: BDR - DDL Locking
Date
Msg-id CAMsr+YGNO-NtJ76DdO0S0yopM_XBj66g1JD29BdZyGUCmz67BA@mail.gmail.com
Whole thread Raw
In response to BDR - DDL Locking  (Will McCormick <wmccormick@gmail.com>)
Responses Re: BDR - DDL Locking
List 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 by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Re: [ADMIN] $libdir/mysql_fdw
Next
From: Adrian Klaver
Date:
Subject: Re: trouble downloading postgres 9.4 for RHEL 6.x