From: | "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Success (Re: page 1 of relation global/11787 was uninitialized) |
Date: | 2013-04-09 17:56:02 |
Message-ID: | 20130409175602.GF12023@cuci.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks, all of you, for all good advice and suggestions.
Andres Freund wrote:
>Afaik debian has never shipped 9.0 in any stable release at all. You can
>use the packages provided by the postgres community though, they are
>compatible:
>http://wiki.postgresql.org/wiki/Apt
I used this to upgrade to 9.0.13, which indeed is fully compatible with
Debian. It started up like a charm. I can upgrade it to 9.1.9 now
(while I'm at it).
For reference, the startup log now looked like this:
LOG: database system was interrupted while in recovery at 2013-04-09 19:45:49 CEST
FATAL: the database system is starting up
HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
LOG: incomplete startup packet
LOG: database system was not properly shut down; automatic recovery in progress
LOG: redo starts at D/B0BAB734
LOG: record with zero length at D/B0D3D71C
LOG: redo done at D/B0D3D6E0
LOG: last completed transaction was at log time 2013-04-09 15:02:24.848947+02
LOG: checkpoint starting: end-of-recovery immediate
LOG: checkpoint complete: wrote 423 buffers (11.8%); 0 transaction log file(s) added, 0 removed, 0 recycled; write=0.003 s, sync=11.419 s, total=11.601 s
So, Tom, thanks for fixing that WAL recovery code :-).
--
Stephen.
From | Date | Subject | |
---|---|---|---|
Next Message | Florian Pflug | 2013-04-09 18:04:52 | Re: Success (Re: page 1 of relation global/11787 was uninitialized) |
Previous Message | Tom Lane | 2013-04-09 17:44:35 | Re: page 1 of relation global/11787 was uninitialized |