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.
[EMAIL PROTECTED]
_______________________________
Do you Yahoo!?
Express yourself with Y! Messenger! Free. Download now.
http://messenger.yahoo.com
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
