| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warning message in standby |
| Date: | 2010-06-29 07:55:01 |
| Message-ID: | AANLkTim16rYAcKYpxRLqmM6tl8rG209PbLgzp8fDVone@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 15, 2010 at 11:35 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On the other hand, I like immediate-panicking. And I don't want the standby
> to retry reconnecting the master infinitely.
On second thought, the peremptory PANIC is not good for HA system. If the
master unfortunately has written an invalid record because of its crash,
the standby would exit with PANIC before performing a failover.
So when an invalid record is found in streamed WAL file, we should keep
the standby running and leave the decision whether the standby retries to
connect to the master forever or shuts down right now, up to the user
(actually, it may be a clusterware)?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thom Brown | 2010-06-29 08:51:44 | Look-behind regular expressions |
| Previous Message | Fujii Masao | 2010-06-29 05:22:44 | Re: suppress automatic recovery after back crash |