Re: postmaster recovery and automatic restart suppression

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Harald (NSN - DE/Munich) Kolb" <harald(dot)kolb(at)nsn(dot)com>, "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 20:04:27
Message-ID: 27793.1244577867@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> "Kolb, Harald (NSN - DE/Munich)" <harald(dot)kolb(at)nsn(dot)com> wrote:
>> 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?

How would that be connected to a "no restart on crash" setting?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-06-09 20:17:19 Re: page is uninitialized --- fixing
Previous Message Greg Stark 2009-06-09 20:03:01 Re: postmaster recovery and automatic restart suppression