| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | Nils Goroll <slink(at)schokola(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SIGFPE handler is naive |
| Date: | 2012-08-14 10:50:52 |
| Message-ID: | CAM-w4HNDbuaKSL3-L9yZgUqKC6bpwi1jZazfLykA=8no2JHETw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It is possible to check if the signal was synchronous or was sent from
an external process. You can check siginfo->si_pid to see who sent you
the signal. I'm not sure checking that and handling it at
check_for_interrupts if it's asynchronous is the best solution or not
though.
I'm a bit confused. Didn't Tom do the laborious process of checking
the whole source tree for situations where there's shared memory
cleanup to be done in and arrange for it to happen? That was the
blocking factor to get pg_cancel_backend() to work. Is the problem
that the sigfpe handler doesn't invoke atexit() handlers?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-08-14 11:25:59 | Re: default_isolation_level='serializable' crashes on Windows |
| Previous Message | Nils Goroll | 2012-08-14 10:28:30 | Re: SIGFPE handler is naive |