From: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Hick ups in Postgresql Logical Replication
Date: Mon, 15 Oct 2018 15:28:08 +1300
Message-ID: <20427d4e-98a5-0cda-bddc-070989015cca@catalyst.net.nz> (raw)
In-Reply-To: <1539447741900-0.post@n3.nabble.com>
References: <1539447741900-0.post@n3.nabble.com>
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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: mark.kirkwood@catalyst.net.nz, pgsql-admin@lists.postgresql.org
Subject: Re: Hick ups in Postgresql Logical Replication
In-Reply-To: <20427d4e-98a5-0cda-bddc-070989015cca@catalyst.net.nz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox