Re: postmaster recovery and automatic restart suppression

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Harald (NSN - DE/Munich) Kolb" <harald(dot)kolb(at)nsn(dot)com>, "ext Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Greg Stark" <stark(at)enterprisedb(dot)com>, "Fujii Masao" <masao(dot)fujii(at)gmail(dot)com>, "Thoralf (NSN - FI/Helsinki) Czichy" <thoralf(dot)czichy(at)nsn(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postmaster recovery and automatic restart suppression
Date: 2009-06-09 19:53:26
Message-ID: 4A2E7766020000250002778B@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kolb, Harald (NSN - DE/Munich)" <harald(dot)kolb(at)nsn(dot)com> wrote:
>> From: ext Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]

>> Mechanism should exist to support useful policy. I don't believe
>> that the proposed switch has any real-world usefulness.

> There are some good reasons why a switchover could be an appropriate
> means in case the DB is facing troubles. It may be that the root
> cause is not the DB itsself, but used resources or other things
> which are going crazy and hit the DB first

Would an example of this be that one drive in a RAID has gone bad and
the hot spare rebuild has been triggered, leading to poor performance
for a while? Is that the sort of issue where you see value?

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-06-09 20:03:01 Re: postmaster recovery and automatic restart suppression
Previous Message Simon Riggs 2009-06-09 19:21:56 Re: postmaster recovery and automatic restart suppression