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

Re: possible bug not in open items

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: possible bug not in open items
Date: 2009-04-09 16:48:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
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."
> > 
> >
> > 
> > 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

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + If your life is a hard drive, Christ can be your backup. +

In response to


pgsql-bugs by date

Next:From: Bruce MomjianDate: 2009-04-09 16:54:27
Subject: Re: BUG #4738: Cannot reconnect to shared memory
Previous:From: Kevin GrittnerDate: 2009-04-09 16:26:52
Subject: Re: Re: [BUGS] BUG #4027: backslash escaping notdisabled inplpgsql

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