Re: EINTR error in SunOS
| От | Greg Stark |
|---|---|
| Тема | Re: EINTR error in SunOS |
| Дата | |
| Msg-id | 87aceg762x.fsf@stark.xeocode.com обсуждение исходный текст |
| Ответ на | Re: EINTR error in SunOS ("Qingqing Zhou" <zhouqq@cs.toronto.edu>) |
| Ответы |
Re: EINTR error in SunOS
|
| Список | pgsql-hackers |
"Qingqing Zhou" <zhouqq@cs.toronto.edu> writes: > The problem of above is if a signal sneaks in, these syscalls will fail. > With a retry, we can fix it. It's a bit stickier than that but only a bit. If you just retry then you're saying users have to use kill -9 to get away from the situation. For some filesystem operations that may be the best we can do. But for most it ought to be possible to CHECK_FOR_INTERRUPTS() and handle the regular signals like C-c or kill -1 normally. Even having the single backend exit (to avoid file resource leaks) is nicer than having to restart the entire instance. -- greg
В списке pgsql-hackers по дате отправления: