WARNING: transaction log file "....." could not be archived: too many failures - Mailing list pgsql-admin

From Joby Joba
Subject WARNING: transaction log file "....." could not be archived: too many failures
Date
Msg-id AANLkTikfgjyieKPAcezuvvro5=iXRD43xkN3Xe5E4b_5@mail.gmail.com
Whole thread Raw
Responses Re: WARNING: transaction log file "....." could not be archived: too many failures
List pgsql-admin
Hello.

The following message appears continuously in the log file of postgresql :

Jan 28 11:35:01 abcd postgres[28359]: [81-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:01 abcd postgres[28359]: [81-2]  code 256
Jan 28 11:35:02 abcd postgres[28359]: [82-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:02 abcd postgres[28359]: [82-2]  code 256
Jan 28 11:35:03 abcd postgres[28359]: [83-1] LOG:  archive command "cp "pg_xlog/000000010000000000000085" /u10/postgres/archive/"000000010000000000000085"" failed: return
Jan 28 11:35:03 abcd postgres[28359]: [83-2]  code 256
Jan 28 11:35:03 abcd postgres[28359]: [84-1] WARNING:  transaction log file "000000010000000000000085" could not be archived: too many failures


The problem is that the requested file is not available anymore. How can I tell postgres to bypass this file ?

Thanks
Joby

pgsql-admin by date:

Previous
From: "Frank Brendel"
Date:
Subject: Re: asm/ia64regs.h not found on FreeBSD 8.1 IA64
Next
From: Bernhard Schrader
Date:
Subject: Re: pg_upgrade 8.3 to 9.0, shutdown is to slow