Re: WARNING: transaction log file "....." could not be archived: too many failures

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Joby Joba" <jobyjoba59(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: WARNING: transaction log file "....." could not be archived: too many failures
Date: 2011-01-28 14:30:58
Message-ID: 4D427EC20200002500039F4E@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Joby Joba <jobyjoba59(at)gmail(dot)com> wrote:

> 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

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

Get a new base backup and start the recovery over. Be sure to fix
whatever broken process caused the WAL file to be discarded while it
might still be needed.

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2011-01-28 15:17:14 Re: asm/ia64regs.h not found on FreeBSD 8.1 IA64
Previous Message Bernhard Schrader 2011-01-28 13:09:46 Re: pg_upgrade 8.3 to 9.0, shutdown is to slow