From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: George Wilk <gwilk@ellacoya.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: missing history file
Date: Fri, 29 Jun 2007 12:12:08 -0500
Message-ID: <4684F718.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <5332.1183135679@sss.pgh.pa.us>
References: <00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com>
<00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com>
<5332.1183135679@sss.pgh.pa.us>
>>> On Fri, Jun 29, 2007 at 11:47 AM, in message <5332.1183135679@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> History files are only created when you do a PITR recovery that stops
> short of the end of WAL (ie, you gave it an explicit stopping point
> criterion). So basically they never appear except by manual
> intervention on the primary server. A standby script should probably
> handle requests for them by looking to see if they're available, and
> returning 'em if so, but not waiting if they are not.
>
> Offhand I would recommend the same strategy for any requested filename
> that's not a plain WAL segment file (ie, all hex digits).
I suspect that it's worth waiting for something like this, too?:
000000010000000A000000CF.0000E744.backup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, gwilk@ellacoya.com, tgl@sss.pgh.pa.us
Subject: Re: missing history file
In-Reply-To: <4684F718.EE98.0025.0@wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox