Re: Question about timelines

From: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
To: Torsten Förtsch <torsten(dot)foertsch(at)gmx(dot)net>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Question about timelines
Date: 2015-07-29 06:28:11
Message-ID: CAJrrPGcXwYnynKNZF-uhVKShB10KXCCo+d+O0iM-+h8-F+fnmg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 29, 2015 at 3:46 PM, Torsten Förtsch
<torsten(dot)foertsch(at)gmx(dot)net> wrote:
> Hi,
>
> we have a complex structure of streaming replication (PG 9.3) like:
>
> master --> replica1
> |
> +-----> replica2 --> replica21
> |
> +------> replica22 --> replica221
>
> Now I want to retire master and make replica2 the new master:
>
> +------> replica1
> |
> replica2 --> replica21
> |
> +------> replica22 --> replica221
>
> replica2 is currently a synchronous replica.
>
> If I "promote" replica2 a new timeline is created. Hence, I have to
> instruct all other replicas to follow that new timeline
> (recovery_target_timeline = 'latest' in recovery.conf).

PostgreSQL 9.3 supports cascade standby to follow automatically the new master
after the timeline switch. In your case even if the timeline is
changed, you need to start
the standby setup for "replica1" only from scratch. All others follows
automatically
the new master.

Regards,
Hari Babu
Fujitsu Australia

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Heikki Linnakangas 2015-07-29 10:42:41 Re: Lots of stuck queries after upgrade to 9.4
Previous Message Torsten Förtsch 2015-07-29 05:46:59 Question about timelines