From: | "Ruth Melendo" <rmelendo(at)teltronic(dot)es> |
---|---|
To: | "'Dave Cramer'" <pg(at)fastcrypt(dot)com> |
Cc: | "'List'" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Lock in bdr |
Date: | 2015-02-27 10:31:59 |
Message-ID: | 003e01d05278$9e0671c0$da135540$@teltronic.es |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Just a mistake.. Sorry
De: davecramer(at)gmail(dot)com [mailto:davecramer(at)gmail(dot)com] En nombre de Dave Cramer
Enviado el: jueves, 26 de febrero de 2015 18:34
Para: Ruth Melendo
CC: List
Asunto: Re: [JDBC] Lock in bdr
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(at)teltronic(dot)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.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2015-02-27 13:43:04 | Re: Can't download tarball "9.4-1201 JDBC Source" |
Previous Message | Pavel Raiskup | 2015-02-27 08:02:53 | Can't download tarball "9.4-1201 JDBC Source" |