From: Tom Lane <tgl@sss.pgh.pa.us>
To: George Wilk <gwilk@ellacoya.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: missing history file
Date: Fri, 29 Jun 2007 12:47:59 -0400
Message-ID: <5332.1183135679@sss.pgh.pa.us> (raw)
In-Reply-To: <00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com>
References: <00d201c7ba61$3f078540$0d7ba8c0@ellacoya.com>
"George Wilk" <gwilk@ellacoya.com> writes:
> When and by what process is the history file being created? My standby
> server seems to be looking for it when put back in the recovery mode, after
> functioning as primary for a while.
> How should I handle missing history file in my script?
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).
regards, tom lane
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: tgl@sss.pgh.pa.us, gwilk@ellacoya.com
Subject: Re: missing history file
In-Reply-To: <5332.1183135679@sss.pgh.pa.us>
* 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