Re: postmaster recovery and automatic restart suppression - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: postmaster recovery and automatic restart suppression
Date
Msg-id 4A2E7766020000250002778B@gw.wicourts.gov
Whole thread Raw
In response to Re: postmaster recovery and automatic restart suppression  ("Kolb, Harald (NSN - DE/Munich)" <harald.kolb@nsn.com>)
Responses Re: postmaster recovery and automatic restart suppression  (Greg Stark <greg.stark@enterprisedb.com>)
Re: postmaster recovery and automatic restart suppression  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
"Kolb, Harald (NSN - DE/Munich)" <harald.kolb@nsn.com> wrote:
>> From: ext Tom Lane [mailto:tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: postmaster recovery and automatic restart suppression
Next
From: Greg Stark
Date:
Subject: Re: postmaster recovery and automatic restart suppression