On Thursday, July 18, 2024, Kashif Zeeshan <kashi.zeeshan@xxxxxxxxx> wrote:
Hi DomenOn Fri, Jul 19, 2024 at 10:57 AM Domen Šetar <domen.setar@xxxxxxx> wrote: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?
Yes you should use the pg_resetwal
Please ignore this advice at this time. The combined inexperience here culminating in using that command is likely to do more harm than good. Figure out why the archiving is failing then make decisions. Maybe you’ll get some admin help with that task for free here, otherwise consider hiring someone with DBA experience to improve your setup.
David J.
