From: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Magnus Hagander" <magnus(at)hagander(dot)net> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg crashing |
Date: | 2008-07-02 12:54:36 |
Message-ID: | 1A6E6D554222284AB25ABE3229A92762E9A68A@nrtexcus702.int.asurion.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
> > Tom Lane wrote:
> >> But the syslogger process (and maybe others) is *not* supposed to
die.
>
> > Right. But are you saying we actually want to start up a new backend
in
> > a directory where we already have a running syslogger (and maybe
others)
> > processes, just no postmaster?
>
> Not great, maybe, but what it looks to me is that the current system
> guarantees that a postmaster with a syslogger child will never recover
> from a backend-child crash. That's not better.
>
When you say "current system", do you mean PG on Windows?
Jon
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-07-02 12:59:24 | Re: pg crashing |
Previous Message | Roberts, Jon | 2008-07-02 12:52:42 | Re: pg crashing |
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2008-07-02 12:59:24 | Re: pg crashing |
Previous Message | Roberts, Jon | 2008-07-02 12:52:42 | Re: pg crashing |