> > Is it possible that the recent change from fork/exec to just fork leaves
> > the postmaster more exposed? I can imagine that it might, but don't have
> > any direct experience with it so am just guessing. Any other ideas? Do
> > people see this on other platforms? This is the first time I can recall
> > seeing the postmaster go away on a crash of a backend (but of course my
> > memory isn't what it should be :)
>
> My guess is that the postmaster can no longer restart its backends after
> one of them aborts. Something I need to check into perhaps.
Does your postmaster stop running, or does it crash any backend that is
started. I am seeing the latter, and the cause appears to be that the
postmaster environment after the restart of the shared memory is not
proper for a backend. I am looking into it.
--
Bruce Momjian | 830 Blythe Avenue
maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)