Thanks! That fixed the issue.
-Original Message-
From: Michael Paquier [mailto:mich...@paquier.xyz]
Sent: Thursday, 8 March 2018 6:41 PM
To: Yavuz Selim Sertoğlu
Cc: Dylan Luong ; pgsql-generallists.postgresql.org
Subject: Re: Resync second slave to new master
On Thu, Mar 08, 2018 at
On Thu, Mar 08, 2018 at 10:48:29AM +0300, Yavuz Selim Sertoğlu wrote:
> If not set, could you add recovery.conf file
> recovery_target_timeline='latest'
> parameter?
> https://www.postgresql.org/docs/devel/static/recovery-target-settings.html
Yes, that's visibly the issue here.
--
Michael
signat
16777216 Mar 8 17:14
> 000601BB00B5
> -rw---. 1 postgres postgres 218 Mar 8 16:48 0006.history
>
> Any ideas?
>
> Dylan
>
> -Original Message-
> From: Michael Paquier [mailto:mich...@paquier.xyz]
> Sent: Tuesday, 6 March 2018 5:55 PM
g
Cc: pgsql-generallists.postgresql.org
Subject: Re: Resync second slave to new master
On Tue, Mar 06, 2018 at 06:00:40AM +, Dylan Luong wrote:
> So everytime after promoting Slave to become master (either manually
> or automatic), just stop Slave2 and run pg_rewind on slave2 against
>
On Tue, Mar 06, 2018 at 06:00:40AM +, Dylan Luong wrote:
> So everytime after promoting Slave to become master (either manually
> or automatic), just stop Slave2 and run pg_rewind on slave2 against
> the new maser (old slave1). And when old master server is available
> again, use pg_rewind on t
original configuration.
-Original Message-
From: Michael Paquier [mailto:mich...@paquier.xyz]
Sent: Tuesday, 6 March 2018 3:54 PM
To: Dylan Luong
Cc: pgsql-generallists.postgresql.org
Subject: Re: Resync second slave to new master
On Tue, Mar 06, 2018 at 04:45:10AM +, Dylan Luong
On Tue, Mar 06, 2018 at 04:45:10AM +, Dylan Luong wrote:
> After a failover (promote) to the Slave1, is it easily resync the
> Slave2 to the new master (old slave1)? Do we need to do full rebuild
> of the Slave2 from new master everytime we failover to Slave1 from
> Master? Can we use pg_rewi
