Re: killing idle instances

From: Andrew Sullivan <andrew(at)libertyrms(dot)info>
To: "pgsql (E-mail)" <pgsql-general(at)postgresql(dot)org>
Subject: Re: killing idle instances
Date: 2003-04-24 21:56:46
Message-ID: 20030424215646.GA8668@libertyrms.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Apr 24, 2003 at 11:09:41AM -0400, Johnson, Shaunn wrote:

> A few nights ago, I was in the middle of building a new
> table when I noticed that there were a lot of idle instances
> and my table was waiting to be built (I believe the message
> statement was WAITING or the like).

The simple <idle> transactions wouldn't cause anyboy to wait.
Something must've been inside a transaction.

> I am looking at the log file for PG and see a lot of 'BackendStartup:
> forked pid=### socket=XXX' messages and I wonder if I
> did the right thing.

That's the connections coming in. Totally normal if you have the
right sort of logging options turned on.

> My question: Should I *not* kill idle processes even though they
> my interfere with building / modifying tables? What are the
> ramifications for such an act?

Truly idle (i.e. not in a transaction) processes shouldn't cause a
problem such as you describe.

A

--
----
Andrew Sullivan 204-4141 Yonge Street
Liberty RMS Toronto, Ontario Canada
<andrew(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-04-24 21:58:35 Re: has_table_priviledge
Previous Message Nigel J. Andrews 2003-04-24 21:53:14 Re: [SQL] rewriting values with before trigger