Re: Hick ups in Postgresql Logical Replication

From: pavan95 <pavan(dot)postgresdba(at)gmail(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: Hick ups in Postgresql Logical Replication
Date: 2018-10-13 16:22:21
Message-ID: 1539447741900-0.post@n3.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi,

I have configured Logical Replication. One Publisher and One Subscriber.
When I query the current LSN on publisher and subscriber, I see that there
is a lag between them.

For example if a published table consists of 3278 records, then on the
subscriber I see only 3275 records. So how to sync that lagged 3 records?

Is there a way to know the number of transaction to be replayed or from
which time the transactions are to be replayed from publisher to subscriber,
with the help of LSN

--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Mark Kirkwood 2018-10-15 02:22:34 Re: Null value returned by function pg_last_wal_receive_lsn() inLogical Replication
Previous Message Shukla, Sumeet 2018-10-12 17:17:50 How should the correct value of shmmax be calculated for DWH (OLAP) server