Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1
Date
Msg-id 27473.1393425545@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1  (Rainer Tammer <pgsql@spg.schulergroup.com>)
Responses Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1
Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1
List pgsql-bugs
Rainer Tammer <pgsql@spg.schulergroup.com> writes:
> void
> StatementCancelHandler(SIGNAL_ARGS)
> {
>         int                     save_errno = errno;
>         elog(WARNING, "StatementCancelHandler() - entered");

> This part is never reached. Does this mean that the signal SIGINT got lost?

Yeah, looks that way.  You might try changing the WARNING to FATAL, as
in your previous example, just to be totally sure that it's not a problem
of the message not getting flushed out or something like that.  But what
it seems at the moment is that the signal isn't getting delivered.

It'd be an idea to add some more logging to CheckStatementTimeout to
verify that (1) MyProcPid corresponds to the process's PID and
(2) the kill() isn't returning an error indication.  You could also
try making it use the non-HAVE_SETSID logic, ie don't use the "-",
just to see if that changes anything.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Sergey Burladyan
Date:
Subject: Re: BUG #9223: plperlu result memory leak
Next
From: Rainer Tammer
Date:
Subject: Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1