From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg crashing |
Date: | 2008-07-02 06:40:44 |
Message-ID: | 4230.1214980844@sss.pgh.pa.us |
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2008-07-02 06:53:47 | Re: Target lists can have at most 1664 entries? |
Previous Message | Magnus Hagander | 2008-07-02 06:34:04 | Re: pg crashing |
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2008-07-02 07:16:30 | Re: Limits of backwards compatibility for psql's \d commands |
Previous Message | Magnus Hagander | 2008-07-02 06:36:08 | Re: Should enum GUCs be listed as such in config.sgml? |