Skip site navigation (1) Skip section navigation (2)

Re: possible bug not in open items

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: possible bug not in open items
Date: 2009-03-27 19:35:53
Message-ID: 49CD2A99.10601@enterprisedb.com (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-03-27 19:43:00
Subject: Re: possible bug not in open items
Previous:From: Heikki LinnakangasDate: 2009-03-27 19:26:15
Subject: Re: possible bug not in open items

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group