Re: BUG #13643: Should a process dying bring postgresql down, or not? - Mailing list pgsql-bugs

From Amir Rohan
Subject Re: BUG #13643: Should a process dying bring postgresql down, or not?
Date
Msg-id trinity-8b056f19-86b2-48f6-a609-40fd31bdd83c-1443479065555@3capp-mailcom-lxa15
Whole thread Raw
In response to Re: BUG #13643: Should a process dying bring postgresql down, or not?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-bugs
> Sent: Tuesday, September 29, 2015 at 12:53 AM
> From: "Alvaro Herrera" <alvherre@2ndquadrant.com>
> To: "Amir Rohan" <amir.rohan@mail.com>
> Cc: pgsql-bugs@postgresql.org
> Subject: Re: [BUGS] BUG #13643: Should a process dying bring postgresql down, or not?

> > > Well, doing things randomly is unlikely to teach you much ...
> >
> > Well, It can teach you which electric socket will
> > electrocute you when poked with a fork. That's useful data.
>
> If you *learn* which one was it, you weren't doing it randomly but
> systematically trying them all.  That's what I wanted to point out.
>

On average, I would have to poke a fork randomly in precisely one socket,
if I payed the bill. But point taken.

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: BUG #13643: Should a process dying bring postgresql down, or not?
Next
From: jasper@ykwc.com
Date:
Subject: BUG #13648: Old Records disappearing after upgrade from 9.4.1 to 9.4.4