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

Re: problem (bug?) when killing client program

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Marcus Andree S(dot) Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: problem (bug?) when killing client program
Date: 2004-03-27 18:01:32
Message-ID: 7133.1080410492@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
"Marcus Andree S. Magalhaes" <marcus(dot)magalhaes(at)vlinfo(dot)com(dot)br> writes:
> Anyway, the fact that a postgres process was alive & kicking & eating
> CPU power after pg_dump exited is a normal behaviour?

Yes; it'll finish out the current command before noticing that the
client connection was dropped.  In this case the current command
happened to be a long-running one ...

If you can reproduce the crash-on-SIGTERM behavior I'd like to know how.
*That*, if real, is a bug.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Reshat SabiqDate: 2004-03-27 18:34:18
Subject: Re: Images in Database
Previous:From: Marcus Andree S. MagalhaesDate: 2004-03-27 17:12:21
Subject: Re: problem (bug?) when killing client program

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