From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | "Magnus Hagander" <mha(at)sollentuna(dot)net>, "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Dave Cramer" <pg(at)fastcrypt(dot)com>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 hard crash problem |
Date: | 2006-10-02 00:23:00 |
Message-ID: | 1740.24.211.165.134.1159748580.squirrel@www.dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
IIRC there is no real SIGINT on Windows, so it can only come from a
postgres program. The windows shutdown could be calling pg_ctl to stop the
service, of course.
cheers
andrew
Joshua D. Drake wrote:
> Magnus Hagander wrote:
>>>> That log entry is the last (of consequence) entry before
>>> the machine says:
>>>> 2006-09-28 16:40:36.921 LOG: received fast shutdown request
>>> Oh? That's pretty interesting on a Windows machine, because
>>> AFAIK there wouldn't be any standard mechanism that might tie
>>> into our homegrown signal facility. Anyone have a theory on
>>> what might trigger a SIGINT to the postmaster, other than
>>> intentional pg_ctl invocation?
>>
>> pg_ctl will send SIGINT to the postmaster when the service is stopped,
>> or when windows is shutting down.
>
> O.k. that pretty much confirms my suspicion then. The SIGINT likely came
> from the user rebooting windows.
>
>>
>> Do you get anything about the postgresql service in the eventlog within
>> say a minute of this happening? (before or after)
>
> Too late to say now :( I will have to follow up with them.
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2006-10-02 00:46:02 | Re: [HACKERS] Numeric overflow problem + patch |
Previous Message | Tom Lane | 2006-10-01 23:25:12 | Re: Select for update with outer join broken? |