RE: wal seams to be corrupted

Hi,

I think, that possible the best solution will be to stop postgresql on problem server (which is replication master), promote secondary, replicate data from promoted secondary back to problem server in make it replication master again. That way I'll get rid of problematic wal file.

Best regards!
[izum]

Domen Šetar
Computer Systems Support
IZUM - Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia
T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/> | domen(dot)setar(at)izum(dot)si<mailto:domen(dot)setar(at)izum(dot)si>

From: Domen Šetar
Sent: Friday, July 19, 2024 7:58 AM
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: wal seams to be corrupted

Hi admins,

The number of wal files on my postgresql server is rising, because it seams that one wal is corrupted. Postgrsql is running normaly. I see this in postgresql log file:

2024-07-19 07:44:12 CEST [2205]: [32288-1] user=,db=,app=,client= DETAIL: The failed archive command was: test ! -f /var/lib/pgsql/ArchiveDir/000000010000044E0000009D && cp pg_wal/000000010000044E0000009D /var/lib/pgsql/ArchiveDir/000000010000044E0000009D

Usualy helped if I deleted wal in ArchiveDir directory. But not this time. Wal is copied again from pg_wal to ArchiveDir directory and error message continues.
What can I do to solve this problem? Is pg_resetwal solution fort his problem? If it is, how to use it?

Best regards!
[izum]

Domen Šetar
Computer Systems Support
IZUM - Institute of Information Science | Prešernova ulica 17 | 2000 Maribor | Slovenia
T: +386 2 25 20 339 | M: +386 41 676 342 | www.izum.si<http://www.izum.si/> | domen(dot)setar(at)izum(dot)si<mailto:domen(dot)setar(at)izum(dot)si>