On Mon, Mar 7, 2011 at 20:16, Heikki Linnakangas
<heikki(dot)linnakangas(at)iki(dot)fi> wrote:
> If recovery_target_timeline is set to 'latest' and standby mode is enabled,
> periodically rescan the archive for new timelines, while waiting for new WAL
> segments to arrive. This allows you to set up a standby server that follows
> the TLI change if another standby server is promoted to master. Before this,
> you had to restart the standby server to make it notice the new timeline.

Can we make recovery_target_timeline='latest' the default when we are
in standby mode? That would suddenly make it a lot easier to "repoint
a slave" after a switchover...

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

• pgsql: If recovery_target_timeline is set to 'latest' and standbymode at 2011-03-07 19:16:05 from Heikki Linnakangas

Responses

• Re: Re: [COMMITTERS] pgsql: If recovery_target_timeline is set to 'latest' and standby mode at 2011-03-07 19:24:56 from Heikki Linnakangas

pgsql-hackers by date

Next:	From: Heikki Linnakangas	Date: 2011-03-07 19:24:56
	Subject: Re: Re: [COMMITTERS] pgsql: If recovery_target_timeline is set to 'latest' and standby mode
Previous:	From: Simon Riggs	Date: 2011-03-07 19:17:25
	Subject: Re: How should the primary behave when the sync standby goes away? Re: Sync Rep v17

pgsql-committers by date

Next:	From: Heikki Linnakangas	Date: 2011-03-07 19:24:56
	Subject: Re: Re: [COMMITTERS] pgsql: If recovery_target_timeline is set to 'latest' and standby mode
Previous:	From: Heikki Linnakangas	Date: 2011-03-07 19:16:05
	Subject: pgsql: If recovery_target_timeline is set to 'latest' and standbymode