Re: BUG #13077: when standby crash and restart, it's need next timeline history file, but upstream node normal.

From: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
To: digoal(at)126(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13077: when standby crash and restart, it's need next timeline history file, but upstream node normal.
Date: 2015-04-17 13:49:35
Message-ID: 55310F6F.4070404@iki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 04/17/2015 06:58 AM, digoal(at)126(dot)com wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13077
> Logged by: digoal
> Email address: digoal(at)126(dot)com
> PostgreSQL version: 9.4.1
> Operating system: CentOS 6.x x64
> Description:
>
> HI,
> I have one primary A,one standby B,another standby C receive wal from
> upstream standby B.
> all it's normal work and all standby catched up to A, But when the last
> standby C crash, and then restart the standby C.
> C need the a new timeline history, and the timeline history really not
> exists any where, I don't promote any standby.
> It's a BUG?

If you never promoted anything, everyone is still on timeline 1. No
timeline history files needed.

- Heikki

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2015-04-18 00:39:02 Re: BUG #13077: when standby crash and restart, it's need next timeline history file, but upstream node normal.
Previous Message Oskari Saarenmaa 2015-04-17 08:50:37 Re: BUG #8470: 9.3 locking/subtransaction performance regression