From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)com> |
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-25 17:18:24 |
Message-ID: | 1179.1393348704@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Rainer Tammer <pgsql(at)spg(dot)schulergroup(dot)com> writes:
> What code path is executed if the timeout passes and
> the signal is send?
Well, the general idea (pre 9.3) is that at the start of the statement,
enable_sig_alarm calculates a future timeout instant and calls setitimer()
to schedule a SIGALRM signal then. When the signal is delivered,
CheckStatementTimeout should do kill(MyProcPid, SIGINT), which should
lead to ProcessInterrupts calling ereport(ERROR), which will longjmp
back to the process idle loop. We need to narrow down which of these
steps is failing to happen before we can speculate much on what's wrong.
There are scenarios in which the SIGINT handler proper won't think it's
safe to call ProcessInterrupts immediately, but will just set a flag
to make that happen later. That should not apply in these test cases,
though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Crowell | 2014-02-25 17:19:15 | Re: BUG #9337: SSPI/GSSAPI with mismatched user names |
Previous Message | Stephen Frost | 2014-02-25 17:07:38 | Re: BUG #9337: SSPI/GSSAPI with mismatched user names |