Date: Fri, 1 Mar 2019 09:46:28 -0800
From: Andres Freund <andres@anarazel.de>
To: tushar <tushar.ahuja@enterprisedb.com>
Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>,
	Robert Haas <robertmhaas@gmail.com>,
	Craig Ringer <craig@2ndquadrant.com>,
	Petr Jelinek <petr@2ndquadrant.com>, pgsql-hackers@postgresql.org
Subject: Re: Minimal logical decoding on standbys
Message-ID: <20190301174628.rjzoi7arvci5ldcm@alap3.anarazel.de>
References: <20181212204154.nsxf3gzqv3gesl32@alap3.anarazel.de>
 <7e905539-7fdc-6b29-5a56-ba48d180fef8@2ndquadrant.com>
 <cbda32d2-eeb6-31b9-a88a-566330a46fc4@enterprisedb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <cbda32d2-eeb6-31b9-a88a-566330a46fc4@enterprisedb.com>
Precedence: bulk

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