Skip site navigation (1) Skip section navigation (2)

Re: Restartable signals 'n all that

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Restartable signals 'n all that
Date: 2008-08-26 20:29:51
Message-ID: 18156.1219782591@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
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
platforms.)

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Robert TreatDate: 2008-08-26 20:46:33
Subject: Re: initdb change
Previous:From: Alvaro HerreraDate: 2008-08-26 19:54:12
Subject: Re: Restartable signals 'n all that

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group