"Qingqing Zhou" <zhouqq(at)cs(dot)toronto(dot)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

In response to

• Re: EINTR error in SunOS at 2006-01-01 06:54:49 from Qingqing Zhou

Responses

• Re: EINTR error in SunOS at 2006-01-01 07:52:48 from Qingqing Zhou

pgsql-hackers by date

Next:	From: Andrew - Supernews	Date: 2006-01-01 07:48:56
	Subject: Re: Removing SORTFUNC_LT/REVLT
Previous:	From: Qingqing Zhou	Date: 2006-01-01 06:54:49
	Subject: Re: EINTR error in SunOS