Where are we on this?
---------------------------------------------------------------------------
Heikki Linnakangas wrote:
> 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."
> >
> > http://www.postgresql.org/docs/8.3/static/server-shutdown.html
> >
> > 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.
>
> --
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +