Re: Restarting standby database have to reaply WAL (redo logs)

I mean before shutdown the last log applied was
0000000100000018000000A5 and after restart pg try to apply from wal
00000001000000180000009D.

The 00000001000000180000009D file is the first wal created in the hot
backup process.

I think that after restarting standby db the first log should be last
log applied + 1

On 9/25/07, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> 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
>
>

--
Ing. César Otero Souto
TE: 54 11 15-6860-2366