Jeff Davis wrote:
> "SIGINT -- The server disallows new connections and sends all existing
> server processes SIGTERM, which will cause them to abort their current
> transactions and exit promptly."
> If you have an open COPY and no data is moving, it simply won't
> terminate it. You can terminate it with ctrl-C from psql, but not a
> SIGINT to the postmaster or a SIGINT or SIGTERM to the backend.
Tracking and grepping for pq_get* functions, there's one more place that
does a blocking read like that: reading the function oid and args in a
fastpath function call. Using v2 protocol. That has got to be deprecated
enough to not worry about :-). Then again, it wouldn't be hard to put
set ImmediateInterruptOK there as well, for the sake of completeness.
In response to
pgsql-bugs by date
|Next:||From: Tom Lane||Date: 2009-03-27 19:43:00|
|Subject: Re: possible bug not in open items |
|Previous:||From: Heikki Linnakangas||Date: 2009-03-27 19:26:15|
|Subject: Re: possible bug not in open items|