restart_lsn is not advancing - Mailing list pgsql-general

From Radoslav Nedyalkov
Subject restart_lsn is not advancing
Date
Msg-id CANhtRiYBMFWLD+XCFi696HppWuh8--fU10K96-c-fuzFnTYgfw@mail.gmail.com
Whole thread Raw
Responses Re: restart_lsn is not advancing
List 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

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device
Next
From: raf
Date:
Subject: Re: PostgreSQL 12 - ERROR: could not rename file "pg_logical/snapshots/1A-7C00D890.snap.13594.tmp" to "pg_logical/snapshots/1A-7C00D890.snap": No space left on device