From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Alex Good *EXTERN*" <alexjsgood(at)gmail(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Recovery continually requests new WAL files |
Date: | 2012-06-13 10:10:56 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C20800B671@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alex Good wrote:
> Although pgpool is involved this isn't actually about pgpool, I've
been
> running through the recovery process manually to try and understand
what
> needs to be done in order to get onlinve recovery working with pgpool.
> Pgpool isn't actually running at the moment.
Oh, I see.
> Anyway, I think what I had misunderstood was the meaning of the
> 'standby_mode' parameter in recovery.conf. If I remove that then the
> process behaves as I expect it to except that the restoring server
ends
> up restoring to a new timeline, I would prefer that it be on the same
> timeline as the master, I have set recovery_target_timeline = 'latest'
> in recovery.conf but this still increments the timeline. Is there any
> way to get the recovery to stay on the same timeline other than
> explicitly specifying the timeline?
That's why I asked if this is about streaming replication.
It is by design that a new timeline is opened after recovery.
This is to tell the WAL sequence from before and after recovery apart.
Is it a problem for you?
Yours,
Laurenz Albe
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Good | 2012-06-13 10:17:23 | Re: Recovery continually requests new WAL files |
Previous Message | Alex Good | 2012-06-13 09:38:27 | Re: Recovery continually requests new WAL files |