From: | "Kolb, Harald (NSN - DE/Munich)" <harald(dot)kolb(at)nsn(dot)com> |
---|---|
To: | "ext Fujii Masao" <masao(dot)fujii(at)gmail(dot)com> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, "Czichy, Thoralf (NSN - FI/Helsinki)" <thoralf(dot)czichy(at)nsn(dot)com> |
Subject: | Re: postmaster recovery and automatic restart suppression |
Date: | 2009-06-05 12:24:55 |
Message-ID: | 8F6635BC27831E4BB0923D8A55136C26018DB6B0@DEMUEXC005.nsn-intra.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
> -----Original Message-----
> From: ext Fujii Masao [mailto:masao(dot)fujii(at)gmail(dot)com]
> Sent: Friday, June 05, 2009 8:14 AM
> To: Kolb, Harald (NSN - DE/Munich)
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] postmaster recovery and automatic
> restart suppression
>
> Hi,
>
> On Fri, Jun 5, 2009 at 1:02 AM, Kolb, Harald (NSN - DE/Munich)
> <harald(dot)kolb(at)nsn(dot)com> wrote:
> > Hi,
> >
> > in case of a serious failure of a backend or an auxiliary
> process the
> > postmaster performs a crash recovery and restarts the db
> automatically.
> >
> > Is there a possibility to deactivate the restart and to
> force the postmaster
> > to simply exit at the end ?
>
> Good point. I also think that this makes a handling of failover
> more complicated. In other words, clusterware cannot determine
> whether to do failover when it detects the death of the primary
> postgres. A wrong decision might cause split brain syndrome.
Mh, I cannot follow your reflections. Could you explain a little bit
more ?
>
> How about new GUC parameter to determine whether to restart
> postmaster automatically when it fails abnormally? This would
> be useful for various failover system.
A new GUC parameter would be the optimal solution.
Since I'm new to the community, what's the "usual" way to make this
happen ?
Regards, Harald.
From | Date | Subject | |
---|---|---|---|
Next Message | pg | 2009-06-05 13:07:46 | Re: Improving the ngettext() patch |
Previous Message | Andrew Dunstan | 2009-06-05 12:19:16 | Re: It's June 1; do you know where your release is? |