Re: Lock in bdr - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Lock in bdr
Date
Msg-id CADK3HHLxr47q5t6L2N4spMetcF8EvYZ=-8VdA2rm8Qr2+cwscg@mail.gmail.com
Whole thread Raw
In response to Lock in bdr  ("Ruth Melendo" <rmelendo@teltronic.es>)
Responses Re: Lock in bdr  ("Ruth Melendo" <rmelendo@teltronic.es>)
List pgsql-jdbc
I'm not sure what this has to do with JDBC ???

Dave Cramer

dave.cramer(at)credativ(dot)ca
http://www.credativ.ca

On 26 February 2015 at 11:34, Ruth Melendo <rmelendo@teltronic.es> wrote:

Hi,

 

I had a lot of problems configuring the DDR env with 2 nodes and now that have it working, It easily gets locked.

My main problem is to get it unlocked. Anybody has experience with that? When it´s locked and you have a record in bdr.bdr_global_locks with state "acquired", which steps do you follow to get unlocked?

HINT: Node (6119460783368684166,1,16384) in the cluster is already performing DDL

That one is because I add a PostGis extension in node1 in Pgadmin and it added correctly and created the table spatial_ref_sys in node 1 but in node 2, tried to add the extension and got an error because the table does not exists. I think that´s a bug because the table adds automatically when you add the extension and it didn´t in node 2.

It´s a hard process to get it work because there is no much doc about it and It´s driving me crazy...

 

Ruth Melendo.


pgsql-jdbc by date:

Previous
From: "Ruth Melendo"
Date:
Subject: Lock in bdr
Next
From: Pavel Raiskup
Date:
Subject: Can't download tarball "9.4-1201 JDBC Source"