| From: | "Fontana Daniel \(Desartec S(dot)R(dot)L(dot)\)" <desartecsrl(at)gmail(dot)com> |
|---|---|
| To: | <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Corrupt WAL in replication slot |
| Date: | 2023-01-04 21:24:57 |
| Message-ID: | 004b01d92083$0048b5b0$00da2110$@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In a replication scheme, one of the satellite databases that replicates
against a consolidated database has one of the WAL files corrupted, more
precisely the 000000010000000000000000009 file.
I try the pg_replication_slot_advance() function to move pg_lsn to skip the
error, but it tells me there is a data inconsistency. You must control the
data consistency even though I want to skip them.
As an observation, the base checkpoint is much further ahead.
Is it possible to regain control of the replication slot?
--
Este correo electrónico ha sido analizado en busca de virus por el software antivirus de Avast.
www.avast.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zheng Li | 2023-01-04 21:35:07 | Re: Support logical replication of DDLs |
| Previous Message | Rébeli-Szabó Tamás | 2023-01-04 21:00:12 | Re: REINDEX vs VACUUM |