Re: Unrecognized configuration parameter in bdr 0.9.3

From: Kaushal Shriyan <kaushalshriyan(at)gmail(dot)com>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Unrecognized configuration parameter in bdr 0.9.3
Date: 2016-02-12 17:59:28
Message-ID: CAD7Ssm_soTK0Eo0jGaTwOoeNCOPCsRreeCpstDBdWVFs+KuM4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Feb 12, 2016 at 7:40 AM, Craig Ringer <craig(at)2ndquadrant(dot)com> wrote:

> On 11 February 2016 at 20:16, Kaushal Shriyan <kaushalshriyan(at)gmail(dot)com>
> wrote:
>
>> Hi,
>>
>> I am following http://bdr-project.org/docs/stable/index.html for setting
>> up multimaster replication.
>>
>
> Are you sure that's the documentation you were using?
>
> You seem to have settings that only applied to the older 0.7.x versions:
>
>
>> # (BEGIN) BDR connection settings for node 1, port 5600
>> bdr.connections = 'secondarymasterport5601'
>> bdr.secondarymasterport5601_dsn = 'dbname=bdrdemo user=postgres port=5601'
>> # (END) BDR connection settings for node 1, port 5600
>>
>> # (BEGIN) BDR connection settings for node 2, port 5601
>> #bdr.connections = '{DevEnvName}node01port5600'
>> #bdr.{DevEnvName}node01port5600_dsn = 'dbname={DevDBName} user=postgres
>> port=5600'
>> #bdr.{DevEnvName}node01port5600_init_replica = on
>> #bdr.{DevEnvName}node01port5600_replica_local_dsn = 'dbname={DevDBName}
>> user=postgres port=5601'
>> # (END) BDR connection settings for node 2, port 5601
>>
>
> The above is not used in BDR 0.9.x. Configuration is done at the SQL level.
>
> --
>

Hi Craig,

Primary Master Postgresql Node ( IP :- 192.168.10.1)

1)psql --port 5600 --username postgres --dbname bdrdemo

2)CREATE EXTENSION btree_gist;
3)CREATE EXTENSION bdr;

*4)SELECT bdr.bdr_group_create(local_node_name := 'node1',node_external_dsn
:= 'port=5600 dbname=bdrdemo');*
5)SELECT bdr.bdr_node_join_wait_for_ready();

Secondary Master Postgresql Node ( IP :- 192.168.10.2)

6)psql --port 5601 --username postgres --dbname bdrdemo

7)CREATE EXTENSION btree_gist;
8)CREATE EXTENSION bdr;

*9)SELECT bdr.bdr_group_join(local_node_name := 'node2',node_external_dsn
:= 'port=5601 dbname=bdrdemo', join_using_dsn := 'port=5600 dbname=bdrdemo'
);*
10)SELECT bdr.bdr_node_join_wait_for_ready();

Based on
http://blog.2ndquadrant.com/dynamic-sql-level-configuration-for-bdr-0-9-0/
since my setup is hosted on two different servers. So if i execute the step
no. 4 in Primary Master Node (IP :- 192.168.10.1) as below

*SELECT bdr.bdr_group_create(local_node_name := 'node1',node_external_dsn
:= 'host **192.168.10.1* *port=5600 dbname=bdrdemo');*

and Step No. 9 in Secondary Master Postgresql Node ( IP :- 192.168.10.2) as
below.

*SELECT bdr.bdr_group_join(local_node_name := 'node2',node_external_dsn :=
'port=5601 dbname=bdrdemo', join_using_dsn := 'host 192.168.10.2 port=5600
dbname=bdrdemo' );*

Are those select statements highlighted in red are supported and correct
and executed at the SQL Level meaning after adding *host **192.168.10.1 in
dsn of Primary Master* and *host **192.168.10.2 in dsn of Secondary Master*?

Please comment.

Thanks in Advance

Regards,

Kaushal

In response to

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2016-02-12 18:57:34 Re: PosgreSQL Security Architecture
Previous Message Pavel Stehule 2016-02-12 17:32:07 Re: XMLEXISTS on legacy XML with malformed xmlns