From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
---|---|
To: | Sylvain MARECHAL <marechal(dot)sylvain2(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: BDR: changing dsn on a running node |
Date: | 2016-10-12 00:39:52 |
Message-ID: | CAMsr+YG32CEPFoknb9zQKEexiEkhYDcyi=TEmOaVwL-_NVtWew@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12 October 2016 at 00:55, Sylvain MARECHAL
<marechal(dot)sylvain2(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Dylan Luong | 2016-10-12 01:04:45 | pgpool fail to load balance after database restart |
Previous Message | Tom Lane | 2016-10-11 23:15:55 | Re: LOG: munmap(0x7fff80000000) failed: Invalid argument |