ode to the third node.
-Selim
From: Sylvain Marechal [marechal.sylva...@gmail.com]
Sent: Sunday, December 06, 2015 4:23 AM
To: Selim Tuvi
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] bdr manual cleanup required
Did you try this :
https://github.com/2ndQuadrant/bdr/issu
x27;t result in
any log messages and the replication was working as it should.
-Selim
From: Craig Ringer [cr...@2ndquadrant.com]
Sent: Sunday, December 06, 2015 7:05 PM
To: Selim Tuvi
Cc: Sylvain MARECHAL; pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR:
I am trying to repair a broken bdr cluster setup and so far everything I tried
failed. Under the original node that ran bdr.bdr_group_create I am getting the
following error:
2015-12-04 19:34:29.063 UTC,,,22991,,5661eac4.59cf,1,,2015-12-04 19:34:28
UTC,3/0,0,ERROR,55000,"previous init failed, m
Yes, bdr_connections had the same number of rows:
deliver=# select * from bdr.bdr_connections;
conn_sysid | conn_timeline | conn_dboid | conn_origin_sysid |
conn_origin_timeline | conn_origin_dboid | conn_is_unidirectional |
[pgsql-general-ow...@postgresql.org]
on behalf of Andreas Kretschmer [andr...@a-kretschmer.de]
Sent: Friday, December 04, 2015 9:59 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR: ALTER statement hanging
> Selim Tuvi hat am 4. Dezember 2015 um 18:46 geschrieben:
>
>
&
ement hanging
Selim Tuvi wrote:
> Hi, I am running a three node BDR cluster. BDR version is 0.9.3. Postgres
> version is 9.4.5.
>
> With 0.9.2, I used to be able to issue ALTER statements using psql and it
> would
> go through. This time it is just hanging. The statement is this:
for
...@postgresql.org [pgsql-general-ow...@postgresql.org]
on behalf of Selim Tuvi [st...@ilm.com]
Sent: Thursday, December 03, 2015 4:31 PM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] ALTER statement hanging
And I tried running the same statement on another node, while one node was
running
running it on another results in a
hang as well.
-Selim
From: Selim Tuvi
Sent: Thursday, December 03, 2015 4:03 PM
To: pgsql-general@postgresql.org
Subject: BDR: ALTER statement hanging
Hi, I am running a three node BDR cluster. BDR version is 0.9.3. Postgres
Hi, I am running a three node BDR cluster. BDR version is 0.9.3. Postgres
version is 9.4.5.
With 0.9.2, I used to be able to issue ALTER statements using psql and it would
go through. This time it is just hanging. The statement is this:
alter table pts alter column shot drop not null;
I also t
Hi we are currently testing BDR 0.9.2 and I set up a two node cluster. From one
node I can run:
select * from bdr.pg_stat_bdr
and it gives me the rows fine but on the other node I get the following error:
ERROR: cache lookup failed for replication identifier id: 4
Any idea why?
The server lo
: Craig Ringer [cr...@2ndquadrant.com]
Sent: Thursday, October 08, 2015 11:05 PM
To: Selim Tuvi
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR: no free replication state could be found
On 9 October 2015 at 06:54, Selim Tuvi wrote:
> Hi I am testing BDR functionality with Postgres 9.4. I
Hi I am testing BDR functionality with Postgres 9.4. I had went through the
bdrdemo example with a 3 node cluster and then tried to set up my own db.
My "max_replication_slots" is set to 6. After getting removing the bdrdemo db I
am having trouble starting up the postgres instance unless I incre
12 matches
Mail list logo
