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 16:03:55 |
Message-ID: | 12409.1215014635@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:
> I'll see if I can repro a case like it to see if the syslogger prevents
> the shared mem from going away when I get back to a dev box. Should be
> enough to just stick a sleep preventing it from stopping, right?
The syslogger isn't restarted at all during a crash --- this isn't
a race-condition scenario.
If there is a race condition here, it must be associated with cleanup
for a process continuing to happen after win32_waitpid has already
reported it dead. Hmm ... how much do we trust that bit of spaghetti
around pgwin32_deadchild_callback? What condition is it really waiting
for?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | jcvlz | 2008-07-02 16:22:51 | Re: simple tool for building web forms |
Previous Message | Magnus Hagander | 2008-07-02 15:55:14 | Re: pg crashing |
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2008-07-02 16:13:52 | Re: PATCH: CITEXT 2.0 |
Previous Message | David Fetter | 2008-07-02 16:01:18 | Re: Explain XML patch v2 |