[BDR] Best practice to automatically abort a DDL operation when one node is down - Mailing list pgsql-general

From Sylvain MARECHAL
Subject [BDR] Best practice to automatically abort a DDL operation when one node is down
Date
Msg-id 569654EA.90602@gmail.com
Whole thread Raw
Responses Re: [BDR] Best practice to automatically abort a DDL operation when one node is down
Re: [BDR] Best practice to automatically abort a DDL operation when one node is down
List pgsql-general
Hello all,

I am using BDR with two nodes 1 and 2.
If I issue a DDL operation in node 1 when node 2 is down, for example:
   CREATE TABLE test (i int PRIMARY KEY); (1)

all other transactions fail with the following error:
   Database is locked against DDL operations

The problem is that the (1) DDL request will wait indefinitely, meaning
all transactions will continue to fail until the DDL operation is
manually aborted (for example, doing CTRL C in psql to abort the "CREATE
TABLE").

What is the best practice to make sure the DDL operation will fail,
possibly after a timeout, if one of the node is down? I could check the
state of the node before issuing the DDL operation, but this solution is
far from being perfect as the node may fail right after this.

Thanks and Regards,
--
Sylvain


pgsql-general by date:

Previous
From: Geoff Winkless
Date:
Subject: Re: WIP: CoC V5
Next
From: Chris Travers
Date:
Subject: Re: WIP: CoC V5