From: | Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org, cbbrowne(at)gmail(dot)com |
Subject: | Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1 |
Date: | 2014-02-26 07:11:14 |
Message-ID: | 530D9392.4090906@spg.schulergroup.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hello,
Just to clarify my picture:
backend process:
tammer 12255262 13107322 0 07:52:10 - 0:00 postgres:
tammer regression [local] SELECT waiting
If I send a SIGINT (-2) to the backend process then this would
be equivalent to the SIGINT send by the SIGALRM handler?
Bye
Rainer
On 25.02.2014 19:47, Tom Lane wrote:
> Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)com> writes:
>> The semop() should be interrupted by SIGINT, right?
> Yeah. Note that we're expecting the SIGINT handler to do a longjmp,
> so that it doesn't matter whether or not the semop would choose to
> resume waiting after a signal. But it has to execute the handler.
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Rainer Tammer | 2014-02-26 07:49:30 | Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1 |
Previous Message | Patrick Wege | 2014-02-26 07:00:10 | Re: BUG #9308: The application failed to initialize properly |