From: | "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> |
---|---|
To: | "pgsql (E-mail)" <pgsql-general(at)postgresql(dot)org> |
Subject: | killing idle instances |
Date: | 2003-04-24 15:09:41 |
Message-ID: | 73309C2FDD95D11192E60008C7B1D5BB04C749BC@snt452.corp.bcbsm.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Running PostgreSQL 7.2.1 on RedHat Linux 7.2.
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).
After considering the urgency of the tables' need to exist
before morning, I killed the idle instances and my process
began to function normally.
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.
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?
Thanks!
-X
From | Date | Subject | |
---|---|---|---|
Next Message | Delao, Darryl W | 2003-04-24 15:28:02 | Postgres Remote Syslog |
Previous Message | David Olbersen | 2003-04-24 14:55:15 | ODBC & Access |