Re: Freeing Connections - Mailing list pgsql-admin

From Lenny Mastrototaro
Subject Re: Freeing Connections
Date
Msg-id 20011018223412.I23213@m1.horizonlive.com
Whole thread Raw
In response to Re: Freeing Connections  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Thu, Oct 18, 2001 at 01:55:33PM -0400, Tom Lane wrote:
> Andrew Hill <list@fornax.net> writes:
> > Normally, 32 connections is heaps for what I need. However, I often get
> > connections that seem to be doing nothing. For example:
>
> > [bash]
> >   \_ postmaster -i -D/var/pgsql/data -N 32 -B 64
> >   \_ [postmaster]
> >   \_ /var/pgsql/bin/postgres 202.174.32.67 postgres anb idle
> >   \_ /var/pgsql/bin/postgres 202.174.32.68 postgres anb idle
> >   \_ [postmaster]
> >   \_ /var/pgsql/bin/postgres 203.34.190.137 postgres bmf idle
> >   \_ [postmaster]
> >   \_ [postmaster]
> >   \_ [postmaster]
> >   \_ [postmaster]
> >   \_ /var/pgsql/bin/postgres 202.174.32.8 radius bmf idle
>
> Curious.  Can you attach to some of the unidentified processes with
> a debugger, and get a stack traceback from 'em?  Offhand I can't
> think of a reason for 7.0 to have any subprocesses that haven't
> changed their PS display.  It would help to know what they are doing.

I believe the processes displayed as [foo] are paged out
which is why you don't see their full commandlines.

Regards,
Lenny

--
Lenny Mastrototaro        VP System Operations       HorizonLive.com
lenny@horizonlive.com  collaborate . interact . learn  (212)813-3867

pgsql-admin by date:

Previous
From: Stephan Szabo
Date:
Subject: Re: VACUUMing a live site OK?
Next
From: Jean-Michel Chabanne
Date:
Subject: Re: PG on Suse