Re: BDR - DDL Locking

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Will McCormick <wmccormick(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: BDR - DDL Locking
Date: 2015-10-21 12:31:35
Message-ID: CAMsr+YGNO-NtJ76DdO0S0yopM_XBj66g1JD29BdZyGUCmz67BA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2015-10-21 13:08:56 Re: trouble downloading postgres 9.4 for RHEL 6.x
Previous Message Devrim GÜNDÜZ 2015-10-21 11:04:19 Re: $libdir/mysql_fdw