From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Dave Cramer <pg(at)fastcrypt(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Win32 hard crash problem |
Date: | 2006-09-30 02:31:21 |
Message-ID: | 451DD6F9.8070608@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
>> O.k. further on this.. the crashing is happening quickly now but not
>> predictably. (as in sometimes a week sometimes 2 days).
>
> OK, that seems to eliminate the GetTickCount-overflow theory anyway.
>
>> 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?
Well the other option would be a windows restart. On windows would that
send a SIGINT to the backend?
Joshua D. Drake
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
--
=== 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 | Bruce Momjian | 2006-09-30 03:12:47 | Re: JAVA Support |
Previous Message | Tom Lane | 2006-09-29 22:15:36 | Re: Per-database search_path |