Re: pg crashing

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:34:04
Message-ID: 486B215C.3010102@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Tom Lane wrote:
> Magnus Hagander <magnus(at)hagander(dot)net> writes:
>> Tom Lane wrote:
>>> Another problem is that postmaster children that do
>>> PGSharedMemoryDetach will still have valid inherited handles for
>>> the shmem segment --- does that factor into the behavior? It looks
>>> to me like the CloseHandle ought to be in PGSharedMemoryDetach.
>
>> Not as long as the processes die. If they die, their handles go with
>> them, and once the reference count goes to zero, the object goes away.
>
> 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? I'd assume we might run into such simple
things as "sharing violations" on the logfile - if nothing inside the db
itself..

//Magnus

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-07-02 06:40:44 Re: pg crashing
Previous Message Tom Lane 2008-07-02 06:26:23 Re: pg crashing

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2008-07-02 06:36:08 Re: Should enum GUCs be listed as such in config.sgml?
Previous Message Tom Lane 2008-07-02 06:26:23 Re: pg crashing