From: | CSN <cool_screen_name90001(at)yahoo(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: idle processes |
Date: | 2004-08-15 04:17:09 |
Message-ID: | 20040815041709.59017.qmail@web52908.mail.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I'm using regular pg_connect's. The processes
eventually went away - was just wondering why they'd
stick around.
CSN
On Saturday 14 August 2004 01:01 pm, CSN wrote:
> 'ps axu' shows:
>
> postgres 1249 0.0 0.7 20200 7296 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
> postgres 1251 0.0 0.6 20196 7036 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
> postgres 1264 0.0 0.3 19936 3200 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
> postgres 1267 0.0 0.2 19936 2992 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
> postgres 1274 0.0 0.2 19936 2996 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
> postgres 1275 0.0 0.2 19936 3000 ? S
> 11:50 0:00 postgres: user1 database1 127.0.0.1
idle
>
> Any idea why these processes are hanging around (for
> about 20 minutes)? There's not any other query
hogging
> that database. Will they eventually timeout?
>
Are you using persistant connections? For example,
with PHP are you using
pg_pconnect instead of pg_connect?
--
Robert C. Paulsen, Jr.
robert(at)paulsenonline(dot)net
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now.
http://messenger.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Paulsen | 2004-08-15 04:43:39 | Re: idle processes |
Previous Message | Paramveer.Singh | 2004-08-15 02:32:14 | postgres error handling mechanism |