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_basebackup -X stream -h main_node_ip -p 5432
-U username -D $PGDATA
po
Primary server:
bdr.connections = 'dr'
bdr.dr_dsn = 'dbname=my_db host=dr_ip user=my_username port=5432'
> What does 'git describe --tags' return?
bdr-pg/REL9_4beta3-1-120-ga2725dd
-Original Message-
From: Andres Freund [mailto:and...@2ndquadran
We have been trying to load our existing database that contains local
sequences into a BDR-based database with global sequences. So, we update our
schema in the new database to USING bdr for all sequences. We make certain
all tables have a primary key. Then we dump our data from our existing
databa
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:
While attempting to alter a table to add a global sequence as a primary key
using the following commands:
CREATE SEQUENCE my_table_id_seq USING bdr;
ALTER TABLE my_table
ADD COLUMN id integer PRIMARY KEY NOT NULL DEFAULT
nextval('my_table_id_seq'::regclass);
I started to notice some issue
aig Ringer wrote:
> On 01/04/2015 12:33 AM, John Casey wrote:
> While attempting to alter a table to add a global sequence as a primary
> key using the following commands:
>
> CREATE SEQUENCE my_table_id_seq USING bdr;
>
> ALTER TABLE my_table
>
> ADD COLUMN id
