Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id EF40E9FA0F9 for ; Tue, 25 Sep 2007 14:05:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 28615-05-2 for ; Tue, 25 Sep 2007 14:05:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from outmail136031.authsmtp.co.uk (outmail136031.authsmtp.co.uk [62.13.136.31]) by postgresql.org (Postfix) with ESMTP id 506879FA1BD for ; Tue, 25 Sep 2007 14:05:51 -0300 (ADT) Received: from outmail128184.authsmtp.net (outmail128184.authsmtp.net [62.13.128.184]) by punt3.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id l8PH5iSc070072; Tue, 25 Sep 2007 18:05:46 +0100 (BST) Received: from [192.168.0.3] (85-211-149-22.dyn.gotadsl.co.uk [85.211.149.22]) (authenticated bits=0) by mail.authsmtp.com (8.13.8/8.13.8/Kp) with ESMTP id l8PH5hnw049986; Tue, 25 Sep 2007 18:05:44 +0100 (BST) Subject: Re: Restarting standby database have to reaply WAL (redo logs) From: Simon Riggs To: Cesar Otero Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Date: Tue, 25 Sep 2007 18:04:25 +0100 Message-Id: <1190739865.4181.507.camel@ebony.site> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2 Content-Transfer-Encoding: 7bit X-Server-Quench: 8da04d77-6b89-11dc-b86a-001185d377ca X-AuthRoute: OCdxZQATClZOTQEd DAteCiNZVAwpPBRK HVkIKg5MJUcNSQVJ NksadBtFagBbflxB HGQLW1NEUVV7WWZ/ bw4fZQBDYEtPQQRu WVZLQE1QERpoT0AJ ZmYbCkc1dwFPcXZ2 K0dqWXEVVBArdUIp RUlJEz8ObHphaTRM TRJQcVJJcANLfxdA PlN4UyBcLwdSbGoL NiMWHhYEdQ9SMzhc WB0MK11aWloCGDI2 VlgOFCkmF0QeSm0z JgIrYkIbVFwcO102 IBMecHZQcwUfBgo8 fkVKDzQYT0FM X-Authentic-SMTP: 61633235383639.squirrel.dmpriest.net.uk:752/Kp X-Report-SPAM: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-Virus-Status: No virus detected - but ensure you scan with your own anti-virus system! X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200709/147 X-Sequence-Number: 26908 On Tue, 2007-09-25 at 12:41 -0300, Cesar Otero wrote: > Then shutdown standby > > ############################################## > WAL file not present yet. Checking for trigger file...2007-09-25 > 12:31:47 ARTLOG: received fast shutdown request > 2007-09-25 12:31:47 ARTFATAL: could not restore file > "0000000100000018000000A6" from archive: return code 15 > 2007-09-25 12:31:47 ARTLOG: startup process (PID 29654) exited with exit code 1 > 2007-09-25 12:31:47 ARTLOG: aborting startup due to startup process failure > 2007-09-25 12:31:47 ARTLOG: logger shutting down The shutdown takes down all processes, so the current restore fails in mid-flight. That's how it works, currently. > And start standby again > Trigger file : /var/lib/postgres/procuracion/standby.trigger > Waiting for WAL file : > /var/lib/postgres/archive/procuracion/00000001000000180000009D > WAL file path : 00000001000000180000009D > Restoring to... : pg_xlog/RECOVERYXLOG > Sleep interval : 5 seconds > Max wait interval : 0 forever > Command for restore : cp > "/var/lib/postgres/archive/procuracion/00000001000000180000009D" > "pg_xlog/RECOVERYXLOG" Then we restart recovery from the last restartpoint. Is that what you meant? -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com