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 15:52:19 |
Message-ID: | 12227.1215013939@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:
> Not likely, but I'd test it anyway. If the issue is related to AV, it's
> certainly fine - you won't be running AV on your Solaris. But more
> importantly, Unix has actual support for signals and not just the fake
> stuff we have on Win32, so it's likely that the postmaster will be
> capable of killing the child processes.
I'm not sure what failure mode you're imagining, but the postmaster has
already verified that all the children that are supposed to be connected
to shared memory are dead before it attempts to recreate shared memory.
So the above sounds completely bogus.
I'm still suspicious of the syslogger holding onto an inherited handle
to the shared-memory file, though that theory would seem to mean that
crash recovery would never work at all on Windows if the syslogger
were enabled. But maybe there is some additional gating factor needed
to cause the problem to manifest.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-07-02 15:55:14 | Re: pg crashing |
Previous Message | Tom Lane | 2008-07-02 15:35:08 | Re: pg_dump - lost synchronization with server: got message type "d", length 6036499 |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2008-07-02 15:55:14 | Re: pg crashing |
Previous Message | Tom Lane | 2008-07-02 15:17:58 | Re: pg crashing |