From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Cesar Otero <cesar(dot)otero(dot)souto(at)gmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Restarting standby database have to reaply WAL (redo logs) |
Date: | 2007-09-25 17:04:25 |
Message-ID: | 1190739865.4181.507.camel@ebony.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Cesar Otero | 2007-09-25 17:14:36 | Re: Restarting standby database have to reaply WAL (redo logs) |
Previous Message | Cesar Otero | 2007-09-25 15:41:26 | Restarting standby database have to reaply WAL (redo logs) |