BDR: Strange values in pg_stat_replication

From: Martin Gudmundsson <martingudmundsson(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: BDR: Strange values in pg_stat_replication
Date: 2014-07-13 21:10:15
Message-ID: A4778E57-3765-4730-9E03-3F6F2A59A314@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi!
I wanted to test synchronous bi-dircetional replication using synchronous_standby_names with bdr.

So I set this up as follows:
Node alpha has the following settings in postgresql.conf

port=5432
wal_level = 'logical'
max_replication_slots = 3
max_wal_senders = 4
synchronous_standby_names=’beta'
shared_preload_libraries = 'bdr'
bdr.connections='beta'
bdr.beta_dsn = ’dbname=bdrdemo username=postgres port=5433'
track_commit_timestamp = on

Node beta has the following settings in postgresql.conf

port=5433
wal_level = 'logical'
max_replication_slots = 3
max_wal_senders = 4
synchronous_standby_names=’alpha'
shared_preload_libraries = 'bdr'
bdr.connections=’alpha'
bdr.alpha_dsn = ’dbname=bdrdemo username=postgres port=5432'
track_commit_timestamp = on§ 1
bdr.alpha_init_replica = on
bdr.alpha_replica_local_dsn = 'dbname=bdrdemo user=postgres port=5432’

It seems to work fine. Bringing down one node stalls the other one, just like synch rep should.

But the view pg_stat_replication view shows async in sync_state column. Shouldn’t this really be sync?

Kind regards, Martin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2014-07-14 02:14:58 Re: Windows Installation User account - Correct database for us
Previous Message Martin Gudmundsson 2014-07-13 20:34:32 Re: Bi-Directional replication client awareness