Re: Minimal logical decoding on standbys - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Minimal logical decoding on standbys
Date
Msg-id 20190301174628.rjzoi7arvci5ldcm@alap3.anarazel.de
Whole thread Raw
In response to Re: Minimal logical decoding on standbys  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: Minimal logical decoding on standbys
List pgsql-hackers
Hi,

On 2019-03-01 13:33:23 +0530, tushar wrote:
> While testing  this feature  found that - if lots of insert happened on the
> master cluster then pg_recvlogical is not showing the DATA information  on
> logical replication slot which created on SLAVE.
> 
> Please refer this scenario -
> 
> 1)
> Create a Master cluster with wal_level=logcal and create logical replication
> slot -
>  SELECT * FROM pg_create_logical_replication_slot('master_slot',
> 'test_decoding');
> 
> 2)
> Create a Standby  cluster using pg_basebackup ( ./pg_basebackup -D slave/ -v
> -R)  and create logical replication slot -
> SELECT * FROM pg_create_logical_replication_slot('standby_slot',
> 'test_decoding');

So, if I understand correctly you do *not* have a phyiscal replication
slot for this standby? For the feature to work reliably that needs to
exist, and you need to have hot_standby_feedback enabled. Does having
that fix the issue?

Thanks,

Andres


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Refactoring the checkpointer's fsync request queue
Next
From: Matt Pulver
Date:
Subject: Infinity vs Error for division by zero