On 4 January 2015 at 02:52, John Casey wrote:
> I'm still experiencing similar problems. I'm not certain what parameter you
> are referring to when you say 'ehost'. Otherwise, I did want to clarify a
> couple of things. I have tried several combinations, each one fails in
> various ways. So ...
x27;t I get the error I posted earlier.
I've attached the new nodes (dr) postgresql.conf file.
-Original Message-
From: 'Andres Freund' [mailto:and...@2ndquadrant.com]
Sent: Wednesday, December 31, 2014 5:04 AM
To: John Casey
Cc: pgsql-general@postgresql.org
Subject: Re:
On 12/30/2014 12:51 PM, John Casey wrote:
> I’ve been having issues while attempting to begin BDR replication. If I
> set up the main node, then use bdr_init_copy, it always fails on second
> node, as shown below.
On a semi-related note, all the BDR node configuration and join support
is currently
Hi,
On 2014-12-30 21:12:17 -0500, John Casey wrote:
>
> > What was your bdr config at this point? The error message indicates that
> it tries to
> > connect to port 5432 on localhost - but the copy was taken from
> 'main_node_ip'.
> > Perhaps you forgot to specify the ehost in the config?
>
> #
t.com]
Sent: Tuesday, December 30, 2014 12:57 PM
To: John Casey
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] bdr_init_copy fails when starting 2nd BDR node
Hi,
On 2014-12-29 23:51:05 -0500, John Casey wrote:
> I've been having issues while attempting to begin BDR replication. If
>
Hi,
On 2014-12-29 23:51:05 -0500, John Casey wrote:
> I've been having issues while attempting to begin BDR replication. If I set
> up the main node, then use bdr_init_copy, it always fails on second node, as
> shown below.
>
>
>
> postgres$ rm -Rf $PGDATA
>
> postgres$ echo db_password | pg_
