| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | "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 19:20:30 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCEA0FC02@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
Do you get anything about the postgresql service in the eventlog within
say a minute of this happening? (before or after)
Could it be a backend or the postmaster trying to send a signal to a
different backend, that for some reason sends it to the wrong process?
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-10-01 22:33:21 | Re: 8.2beta1 failure on IRIX |
| Previous Message | Magnus Hagander | 2006-10-01 19:14:35 | Re: src/tools/msvc usage instructions |