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 |             
              
                     conn_dsn                                                | 
conn_apply_delay | conn_replication_sets                                        
       
---------------------+---------------+------------+-------------------+----------------------+-------------------+------------------------+---------------------------
-----------------------------------------------------------------------------+------------------+-----------------------
                                              
 6212648563684174798 |             1 |     533136 | 0                 |         
           0 |                 0 | f                      | 
host=pe-deliverdb-sf-01v port=5432 dbname=deliver user=deliver_admin 
password=xxxxx   |                  | {default}                                 
                          
 6223770712502831127 |             1 |      16389 | 0                 |         
           0 |                 0 | f                      | 
host=pe-deliverdb-sing-01v port=5432 dbname=deliver user=deliver_admin 
password=xxxxx |                  | {default}                                   
                        
 6223800735012265413 |             1 |      16389 | 0                 |         
           0 |                 0 | f                      | 
host=pe-deliverdb-lon-01v port=5432 dbname=deliver user=deliver_admin 
password=xxxxx  |                  | {default}                                  
                         
(3 rows)   

One other thing I noticed is that the conn_dboid is the same for two of the 
nodes. Is that normal?

-Selim

________________________________________
From: pgsql-general-ow...@postgresql.org [pgsql-general-ow...@postgresql.org] 
on behalf of Sylvain MARECHAL [marechal.sylva...@gmail.com]
Sent: Friday, December 04, 2015 10:14 AM
To: pgsql-general@postgresql.org
Subject: Re: [GENERAL] BDR: ALTER statement hanging

Le 04/12/2015 18:59, Andreas Kretschmer a écrit :
>
>
> I think, the state 'i' is the main reason for your problem, because of: "i-
> Joining: The node is doing initial slot creation or an initial dump and load".
>
> But i can't tell you why this nodes are in this state.
>
>
> Regards, Andreas
>
>
Did-you check the bdr.bdr_connections table?
It should have as many lines as the bdr.bdr_nodes tables.

Sylvain


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Reply via email to