Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Tom Lane wrote:
>> So we've got two problems: SA_RESTART is preventing some EINTRs from
>> happening when we'd like, and yet it seems we are at risk of unwanted
>> EINTRs anyway.
>> The only really clean solution I can see is to stop using SA_RESTART
>> and try to make all our syscalls EINTR-proof. But the probability
>> of bugs-of-omission seems just about 100%, especially in third party
>> backend add-ons that we don't get to review the code for.
> Did we do anything about this? I see we have it on TODO ...
No, I haven't done anything about it.
(I'm not entirely convinced that there's a real problem on any modern
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Robert Treat||Date: 2008-08-26 20:46:33|
|Subject: Re: initdb change|
|Previous:||From: Alvaro Herrera||Date: 2008-08-26 19:54:12|
|Subject: Re: Restartable signals 'n all that|