Re: possible bug not in open items
От | Heikki Linnakangas |
---|---|
Тема | Re: possible bug not in open items |
Дата | |
Msg-id | 49CD2A99.10601@enterprisedb.com обсуждение исходный текст |
Ответ на | Re: possible bug not in open items (Jeff Davis <pgsql@j-davis.com>) |
Ответы |
Re: possible bug not in open items
|
Список | pgsql-bugs |
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
В списке pgsql-bugs по дате отправления: