From: | Radoslav Nedyalkov <rnedyalkov(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | restart_lsn is not advancing |
Date: | 2020-06-30 23:09:45 |
Message-ID: | CANhtRiYBMFWLD+XCFi696HppWuh8--fU10K96-c-fuzFnTYgfw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello All,
we are in a situation where restart_lsn for logical replication slots is
not advancing.
We have two slots. Both are active, confirmed_flush_lsn also is updated.
Client side all looks okay. remote_lsn for subscritions is advancing.
The effect of restart_lsn being 'stopped' is the disk is filling up.
Any idea what could be the cause?
We will try to re-establish replication by dropping current slots ,
although we have to do it very carefully. We should avoid initial loading
(these are 4T of data)
Thanks and regards,
Rado