RE: wal seams to be corrupted - Mailing list pgsql-admin
Thanks for the answer.
What about to stop postgresql server which is primary in replication and promote another server?
Best regards!
| Domen Šetar |
From: Kashif Zeeshan <kashi.zeeshan@gmail.com>
Sent: Friday, July 19, 2024 8:10 AM
To: Domen Šetar <domen.setar@izum.si>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: wal seams to be corrupted
Hi Domen
On Fri, Jul 19, 2024 at 10:57 AM Domen Šetar <domen.setar@izum.si> 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 what it does is clears the write-ahead log (WAL) and optionally resets some other control information stored in the pg_control file. This function is sometimes needed if these files have become corrupted. It should be used only as a last resort, when the server will not start due to such corruption.
You can find the help from the following link
Regards
Kashif Zeeshan
Best regards!
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 | domen.setar@izum.si
Attachment
pgsql-admin by date: