Re: Problem with PostgreSQL 9.2.7 and make check on AIX 7.1

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-26 14:39:05
Message-ID: 27473.1393425545@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:
> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Sandro Santilli 2014-02-26 15:01:13 Re: Uninterruptable regexp_replace in 9.3.1 ?
Previous Message Cyriac Joseph Maliyil 2014-02-26 13:11:44 Re: BUG #9333: The PostgreSQL service stops unexpectedly