Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id F1F6B2E49DD for ; Fri, 11 Jan 2008 16:28:19 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 78882-10 for ; Fri, 11 Jan 2008 16:28:15 -0400 (AST) Received: from mail2.yozons.com (mail2.yozons.com [63.251.168.97]) by postgresql.org (Postfix) with ESMTP id AF98E2E453C for ; Fri, 11 Jan 2008 16:28:15 -0400 (AST) Received: from [192.168.1.2] (pool-71-164-18-27.sttlwa.fios.verizon.net [71.164.18.27]) (authenticated bits=0) by mail2.yozons.com (8.12.10/8.12.10) with ESMTP id m0BKSElG026702 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Fri, 11 Jan 2008 12:28:14 -0800 Message-ID: <4787D161.9000000@computer.org> Date: Fri, 11 Jan 2008 12:28:17 -0800 From: David Wall Reply-To: d.wall@computer.org User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Re: WAL recovery, stop and resume recovery? References: <4787C7A7.3000503@computer.org> In-Reply-To: <4787C7A7.3000503@computer.org> Content-Type: multipart/alternative; boundary="------------060305090000020206030902" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/124 X-Sequence-Number: 27898 This is a multi-part message in MIME format. --------------060305090000020206030902 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit > LOG: database system was shut down at 2008-01-11 11:40:05 PST > LOG: starting archive recovery > LOG: restore_command = "~/postgresql/bin/pg_standby -l -d -s 2 -k 20 > -t ~/postgresql/restoreWALs/STOP_RESTORE ~/postgresql/restoreWALs %f > %p 2>> ~/pg_standby.log" > *LOG: restored log file "00000001000000050000001D" from archive > LOG: invalid record length at 5/1D000068 > LOG: invalid primary checkpoint record > LOG: restored log file "00000001000000050000001D" from archive > LOG: invalid resource manager ID in secondary checkpoint record > PANIC: could not locate a valid checkpoint record* > LOG: startup process (PID 9219) was terminated by signal 6 > LOG: aborting startup due to startup process failure > LOG: logger shutting down One more thing is that the error above about the 1D log file above having an invalid record length, etc. is interesting in that if I restore from the TAR backup created for this and start the backup database in recover mode, it manages to process the 1D log file just fine (along with all the previous log files of course). David --------------060305090000020206030902 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
LOG:  database system was shut down at 2008-01-11 11:40:05 PST
LOG:  starting archive recovery
LOG:  restore_command = "~/postgresql/bin/pg_standby -l -d -s 2 -k 20 -t ~/postgresql/restoreWALs/STOP_RESTORE ~/postgresql/restoreWALs %f %p 2>> ~/pg_standby.log"
LOG:  restored log file "00000001000000050000001D" from archive
LOG:  invalid record length at 5/1D000068
LOG:  invalid primary checkpoint record
LOG:  restored log file "00000001000000050000001D" from archive
LOG:  invalid resource manager ID in secondary checkpoint record
PANIC:  could not locate a valid checkpoint record

LOG:  startup process (PID 9219) was terminated by signal 6
LOG:  aborting startup due to startup process failure
LOG:  logger shutting down

One more thing is that the error above about the 1D log file above having an invalid record length, etc. is interesting in that if I restore from the TAR backup created for this and start the backup database in recover mode, it manages to process the 1D log file just fine (along with all the previous log files of course).

David
--------------060305090000020206030902--