From: | Joshua Colson <joshua(dot)colson(at)ination(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Change "shutdown time" was: Change "database system |
Date: | 2006-12-15 15:23:16 |
Message-ID: | 1166196196.6761.9.camel@s60r.ination.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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(dot)colson(at)ination(dot)com>
iNation, LLC
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-12-15 15:44:34 | Re: out of memory in backup and restore |
Previous Message | Shoaib Mir | 2006-12-15 13:47:59 | Re: invalid types and tables |