Postgres Pro
Downloads
Home   >   mailing lists

Re: restart_lsn is not advancing - Mailing list pgsql-general

From Radoslav Nedyalkov
Subject Re: restart_lsn is not advancing
Date
Msg-id CANhtRib0Of+1Barw3-60mMw2GqvmDbj3DBL_0AVwbGYn-7=cCw@mail.gmail.com
Whole thread Raw
In response to restart_lsn is not advancing  (Radoslav Nedyalkov <rnedyalkov@gmail.com>)
List pgsql-general
Tree view
one more detail:  pg_replication_slots.catalog_xmin shows the biggest age in the system. 
How could  transaction on catalogues may affect logical slot. Any clue  here ?
Thank you,
Rado

On Wed, Jul 1, 2020 at 2:09 AM Radoslav Nedyalkov <rnedyalkov@gmail.com> wrote:
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: 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
Next
From: FOUTE K. Jaurès
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