From: Joshua Colson <joshua.colson@ination.com>
To: pgsql-admin@postgresql.org
Subject: Re: Change "shutdown time" was: Change "database system
Date: Fri, 15 Dec 2006 08:23:16 -0700
Message-ID: <1166196196.6761.9.camel@s60r.ination.com> (raw)
In-Reply-To: <29504.1166141419@sss.pgh.pa.us>
References: <1166139640.7183.27.camel@s60r.ination.com>
<29504.1166141419@sss.pgh.pa.us>
On Thu, 2006-12-14 at 19:10 -0500, Tom Lane wrote:
> You'd have to modify pg_resetxlog to force that value into the sysid
> rather than whatever is there. Hand-editing wouldn't work very well
> because of (a) the CRC on pg_control and (b) the need to copy the
> value into extant WAL segments.
Well, I ended up just using the pg_control file from the running
installation. The seemed to work in combination with pg_resetxlog but
now the restore is not working because the postmaster has a shutdown
timestamp of today's date and the recovery is thinking that it has
already recovered past the proper point in time. :(
Does anyone know how I can convince the postmaster to believe it was
shutdown at approximately the time the pg_dumpall happened?
Thank you all again for any assistance!
--
Joshua Colson <joshua.colson@ination.com>
iNation, LLC
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: joshua.colson@ination.com
Subject: Re: Change "shutdown time" was: Change "database system
In-Reply-To: <1166196196.6761.9.camel@s60r.ination.com>
References: <1166139640.7183.27.camel@s60r.ination.com> <29504.1166141419@sss.pgh.pa.us> <1166196196.6761.9.camel@s60r.ination.com>
* 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