Does pglogical support PG 9.4.5?

From: leo <dazhoufei(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Does pglogical support PG 9.4.5?
Date: 2016-01-27 02:42:37
Message-ID: 1453862557014-5884352.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi all,

I am test pglogical on PG 9.4.5, but I am not successfully even if I
install the latest version "postgresql94-pglogical-1.0.1-2".
Is there any one running pglogical on PG 9.4.5 successfully?
I describe my operation step, please help me to trouble shooting?

provider node: 10.10.10.11
subscriber node: 10.10.10.103

Config pg_hba.conf on provider node:

host all postgres 0.0.0.0/0 trust
host replication postgres 10.10.10.103/0 trust

Config pg_hba.conf on subscriber node:

host all postgres 0.0.0.0/0 trust
host replication postgres 10.10.10.11/0 trust

Config the postgres.conf according to README

1. Create subscribe node:
Provider: 10.10.10.11
SELECT pglogical.create_node(node_name := 'subscriber_test_3',dsn :=
'hostaddr= 10.10.10.103 port=5509 dbname=testdb user=postgres');
create_node
-------------
2393536845

2. Create replication ser
select pglogical.create_replication_set('replicate_gis_data', true, true,
true, true);
create_replication_set
------------------------
2904604760

3. Add table into replication set

select
pglogical.replication_set_add_table('replicate_gis_data','test_table',
true);

===========Executing on subscriber node
Enable the network connection on:
enbale network connection and replication connection without password

1. Create provider:
SELECT pglogical.create_node(node_name := 'provider_test_2',dsn :=
'hostaddr= 10.10.10.11 port=5508 dbname=testdb user=postgres');
create_node
-------------
3082486013

2. Create subscription to provider noede, executing on subscribe node

select pglogical.create_subscription('replicate_gis_data_from_11',
'hostaddr= 10.10.10.11 port=5508 dbname=testdb
user=postgres',E'{"replicate_gis_data"}');

Error Message on subscriber node
===================

< 2016-01-12 19:45:41.396 UTC >DEBUG: shmem_exit(1): 2 before_shmem_exit
callbacks to make
< 2016-01-12 19:45:41.396 UTC >DEBUG: shmem_exit(1): 6 on_shmem_exit
callbacks to make
< 2016-01-12 19:45:41.396 UTC >DEBUG: proc_exit(1): 2 callbacks to make
< 2016-01-12 19:45:41.396 UTC >DEBUG: exit(1)
< 2016-01-12 19:45:41.396 UTC >DEBUG: shmem_exit(-1): 0 before_shmem_exit
callbacks to make
< 2016-01-12 19:45:41.396 UTC >DEBUG: shmem_exit(-1): 0 on_shmem_exit
callbacks to make
< 2016-01-12 19:45:41.396 UTC >DEBUG: proc_exit(-1): 0 callbacks to make
< 2016-01-12 19:45:41.397 UTC >DEBUG: reaping dead processes
< 2016-01-12 19:45:41.397 UTC >LOG: worker process: pglogical apply
26429:2377587811 (PID 967) exited with exit code 1
< 2016-01-12 19:45:41.397 UTC >DEBUG: StartTransaction
< 2016-01-12 19:45:41.397 UTC >LOG: unregistering background worker
"pglogical apply 26429:2377587811"
< 2016-01-12 19:45:41.397 UTC >DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.397 UTC >LOG: registering background worker
"pglogical apply 26429:2377587811"
< 2016-01-12 19:45:41.397 UTC >LOG: starting background worker process
"pglogical apply 26429:2377587811"
< 2016-01-12 19:45:41.397 UTC >DEBUG: CommitTransaction
< 2016-01-12 19:45:41.397 UTC >DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.397 UTC >DEBUG: find_in_dynamic_libpath: trying
"/usr/pgsql-9.4/lib/pglogical"
< 2016-01-12 19:45:41.397 UTC >DEBUG: find_in_dynamic_libpath: trying
"/usr/pgsql-9.4/lib/pglogical.so"
< 2016-01-12 19:45:41.397 UTC >DEBUG: InitPostgres
< 2016-01-12 19:45:41.397 UTC >DEBUG: my backend ID is 8
< 2016-01-12 19:45:41.397 UTC >DEBUG: StartTransaction
< 2016-01-12 19:45:41.397 UTC >DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.397 UTC >DEBUG: CommitTransaction
< 2016-01-12 19:45:41.397 UTC >DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.397 UTC >DEBUG: StartTransaction
< 2016-01-12 19:45:41.398 UTC >DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.398 UTC >DEBUG: CommitTransaction
< 2016-01-12 19:45:41.398 UTC >DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.398 UTC >DEBUG: StartTransaction
< 2016-01-12 19:45:41.398 UTC >DEBUG: name: unnamed; blockState:
DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.398 UTC >DEBUG: CommitTransaction
< 2016-01-12 19:45:41.398 UTC >DEBUG: name: unnamed; blockState:
STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
< 2016-01-12 19:45:41.398 UTC >ERROR: subscriber replicate_gis_data_from_11
initialization failed during nonrecoverable step (s), please try the setup
again

=========Some error messages are raised on provide node after I create
subscription on subscription node. For example:

LOG: exported logical decoding snapshot: "0003F485-1" with 0 transaction
IDs
ERROR: schema "topology" already exists
LOG: unexpected EOF on client connection with an open transaction
LOG: logical decoding found consistent point at 4F/8CD1A6B0
DETAIL: There are no running transactions.
LOG: exported logical decoding snapshot: "0003F488-1" with 0 transaction
IDs
ERROR: schema "topology" already exists
LOG: unexpected EOF on client connection with an open transaction

--
View this message in context: http://postgresql.nabble.com/Does-pglogical-support-PG-9-4-5-tp5884352.html
Sent from the PostgreSQL - general mailing list archive at Nabble.com.

Browse pgsql-general by date

  From Date Subject
Next Message Josh Berkus 2016-01-27 05:11:07 Code of Conduct plan
Previous Message Josh Berkus 2016-01-26 20:57:04 Re: Can PostgreSQL use multi-column index for FK constraint validation?