pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Effects of IDLE processes
Date: Sun, 20 Feb 2005 22:18:31 -0500
Message-ID: <m3r7jaa9dk.fsf@knuth.knuth.cbbrowne.com> (raw)
References: <200502181815.17000.jerome@gmanmi.tv>
	<4219304A.1070408@bigfoot.com>

After a long battle with technology, Gaetano Mendola <mendola@bigfoot.com>, an earthling, wrote:
> JM wrote:
>> Hi ALL,
>> 
>> 	I was wondering if there is a DB performance reduction if
>> there are a lot of IDLE processes.
>> 
>> 30786 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>> 32504 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>> 32596 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  1722 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  1724 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  3881 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  6332 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  6678 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  6700 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  6768 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  8544 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  8873 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  8986 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9000 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9010 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9013 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9016 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9019 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>>  9020 ?        S      0:00 postgres: user1 gmadb 10.10.10.1 idle
>> 

> In my experience not at all, you have to wonder if some of that are
> "idle in transaction" that are really a pain in the @#$

I'd be concerned about "idle" processes insofar as they are holding on
to _some_ memory that isn't shared.

"idle in transaction" is quite another matter; long-running
transactions certainly do lead to evil.  When running Slony-I, for
instance, "idle in transaction" means that pg_listener entries are
being held onto so they cannot be vacuumed out, and that's only one
example of a possible evil...
-- 
(reverse (concatenate 'string "moc.liamg" "@" "enworbbc"))
http://linuxdatabases.info/info/languages.html
You know  how most packages say  "Open here". What is  the protocol if
the package says, "Open somewhere else"?



view thread (5+ messages)  latest in thread

Message-ID: <m3r7jaa9dk.fsf@knuth.knuth.cbbrowne.com>
Permalink:  ../m3r7jaa9dk.fsf@knuth.knuth.cbbrowne.com/
Also on:    postgresql.org/message-id/m3r7jaa9dk.fsf@knuth.knuth.cbbrowne.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Effects of IDLE processes
  In-Reply-To: <m3r7jaa9dk.fsf@knuth.knuth.cbbrowne.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox