From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming replication and triggering failover |
Date: | 2010-01-08 13:41:00 |
Message-ID: | 3f0b79eb1001080541g41e6ebc0ne1d587cf9aa63cc1@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jan 8, 2010 at 10:31 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Fujii Masao wrote:
>> You dropped CheckForStandbyTrigger() called at the end of recovery.
>> I think that this would be problem when an invalid record is found before
>> we reaches a streaming recovery state. The standby would be out-of-control
>> of the clusterware, and be brought up. Which might cause a split-brain
>> syndrome. We should need something to prevent such unexpected
>> activation?
>
> I modified ReadRecord to PANIC if an invalid record is found during
> streaming recovery.
Oh, sorry. It was my misunderstanding :(
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Filip Rembiałkowski | 2010-01-08 13:48:23 | Re: [GENERAL] pg.dropped |
Previous Message | Tom Lane | 2010-01-08 13:37:45 | Re: Why doesn't query_tree_walker examine the intoClause field? |