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

From: digoal(at)126(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #13077: when standby crash and restart, it's need next timeline history file, but upstream node normal.
Date: 2015-04-17 03:58:56
Message-ID: 20150417035856.5198.53331@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Oskari Saarenmaa 2015-04-17 08:50:37 Re: BUG #8470: 9.3 locking/subtransaction performance regression
Previous Message Bruce Momjian 2015-04-17 01:35:47 Re: BUG #13042: pg_upgrade --check succeeded but run failed due to missing thesaurus file