From: Tom Lane <tgl@sss.pgh.pa.us>
To: Brendan Duddridge <brendan@clickspace.com>
Cc: Jeff Frost <jeff@frostconsultingllc.com>
Cc: PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: Recovery will take 10 hours
Date: Thu, 20 Apr 2006 19:29:49 -0400
Message-ID: <1203.1145575789@sss.pgh.pa.us> (raw)
In-Reply-To: <DC0482D0-231B-4550-BE11-A4C110E844E9@clickspace.com>
References: <85A15B2E-F59C-4FEF-82D4-61F48ABDCDE5@clickspace.com>
<Pine.LNX.4.64.0604201419130.1527@glacier.frostconsultingllc.com>
<BCAE93E6-B799-4B6F-9F78-AA694342A169@clickspace.com>
<DC0482D0-231B-4550-BE11-A4C110E844E9@clickspace.com>
Brendan Duddridge <brendan@clickspace.com> writes:
> Oops... forgot to mention that both files that postgres said were
> missing are in fact there:
Please place the blame where it should fall: it's your archive restore
command that's telling postgres that.
> There didn't seem to be any issues with the NFS mount. Perhaps it
> briefly disconnected and came back right away.
Unstable NFS mounts are Really Bad News. You shouldn't be expecting
to run a stable database atop such a thing.
If it's not the database but only the WAL archive that's NFS'd, it might
be possible to live with it, but you'll need to put some defenses into
your archive restore script to cope with such events.
As far as restarting goes: I think you can restart from here without
first redoing your base-backup restore, but as previously noted it'll
still read through the same WAL files it looked at before. You won't
save much except the time to redo the base restore.
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-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, brendan@clickspace.com, jeff@frostconsultingllc.com
Subject: Re: Recovery will take 10 hours
In-Reply-To: <1203.1145575789@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