| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-01 22:45:57 |
| Message-ID: | 45204525.8000403@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Sincerely,
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-10-01 23:13:02 | Re: Select for update with outer join broken? |
| Previous Message | Joshua D. Drake | 2006-10-01 22:44:35 | Re: libedit broke in head |