Re: postmaster recovery and automatic restart suppression
От | Kolb, Harald (NSN - DE/Munich) |
---|---|
Тема | Re: postmaster recovery and automatic restart suppression |
Дата | |
Msg-id | 8F6635BC27831E4BB0923D8A55136C26018DB6B0@DEMUEXC005.nsn-intra.net обсуждение исходный текст |
Ответ на | Re: postmaster recovery and automatic restart suppression (Fujii Masao <masao.fujii@gmail.com>) |
Ответы |
Re: postmaster recovery and automatic restart suppression
|
Список | pgsql-hackers |
Hi, > -----Original Message----- > From: ext Fujii Masao [mailto:masao.fujii@gmail.com] > Sent: Friday, June 05, 2009 8:14 AM > To: Kolb, Harald (NSN - DE/Munich) > Cc: pgsql-hackers@postgresql.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.kolb@nsn.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.
В списке pgsql-hackers по дате отправления: