Re: BDR: changing dsn on a running node - Mailing list pgsql-general

From Craig Ringer
Subject Re: BDR: changing dsn on a running node
Date
Msg-id CAMsr+YG32CEPFoknb9zQKEexiEkhYDcyi=TEmOaVwL-_NVtWew@mail.gmail.com
Whole thread Raw
In response to Re: BDR: changing dsn on a running node  (Sylvain MARECHAL <marechal.sylvain2@gmail.com>)
List pgsql-general
On 12 October 2016 at 00:55, Sylvain MARECHAL
<marechal.sylvain2@gmail.com> wrote:
> Le 07/10/2016 à 23:54, Natan Abolafya a écrit :
>
> Is it possible to change the dsn connection string of a node without leaving
> the group? I couldn’t find the related documentation unfortunately.
>
> We’re using BDR in a dynamic environment where the hostname/ip of a node may
> be changed any time. Leaving and rejoining the BDR group seems to be a
> solution but is a bit tedious and a slow process.

You can update the bdr.bdr_connections entry and then kill the apply workers.

Right now bdr.bdr_connections_changed() doesn't know to check for a
changed DSN. I'd welcome a patch to address that, since I probably
won't have time to get to it soon.

We should have a bdr.bdr_connection_set_dsn(...) function, really.
Again, a patch would be welcomed.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: LOG: munmap(0x7fff80000000) failed: Invalid argument
Next
From: Dylan Luong
Date:
Subject: pgpool fail to load balance after database restart