Re: Hick ups in Postgresql Logical Replication - Mailing list pgsql-admin

From Mark Kirkwood
Subject Re: Hick ups in Postgresql Logical Replication
Date
Msg-id 20427d4e-98a5-0cda-bddc-070989015cca@catalyst.net.nz
Whole thread Raw
In response to Re: Hick ups in Postgresql Logical Replication  (pavan95 <pavan.postgresdba@gmail.com>)
Responses Re: Hick ups in Postgresql Logical Replication  (pavan95 <pavan.postgresdba@gmail.com>)
List pgsql-admin
Hi,

A lag would suggest that the subscriber is still catching up. However, 
there might be something else going on. We'd probably need to see how 
you actually did your set up, and also how you are deducing that there 
is a lag (e.g pg_stat_subscription)?

Don't forget to examine your logs for errors too.

regards

Mark


On 14/10/18 05:22, pavan95 wrote:
> 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
>



pgsql-admin by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Null value returned by function pg_last_wal_receive_lsn()inLogical Replication
Next
From: prasanna rk
Date:
Subject: Commit not required for update statement