Re: Understanding ps -ef "command" column - Mailing list pgsql-general

From David Jaquay
Subject Re: Understanding ps -ef "command" column
Date
Msg-id ad4aa5a80802220904s23dfd7efq2449a38c5b75a5e1@mail.gmail.com
Whole thread Raw
In response to Understanding ps -ef "command" column  ("David Jaquay" <djaquay@gmail.com>)
List pgsql-general
On the one hand, that's pretty cool.  I keep forgetting that's out there.

On the other hand, I know what process is holding the connection; it's the only one on the box connecting to that server.  So lsof doesn't let me connect a process on the server to a connection object (one of many) on the client.

Thanks just the same, tho,

Dave


On Fri, Feb 22, 2008 at 11:55 AM, Erik Jones <erik@myemma.com> wrote:

On Feb 22, 2008, at 10:28 AM, Douglas McNaught wrote:

> On 2/22/08, David Jaquay <djaquay@gmail.com> wrote:
>> When I do a ps -ef, in the command column, I see:
>>
>> postgres: postgres dbname 10.170.1.60(57413) idle
>>
>> I get all of this, except the "57413".  What does this mean, and more
>> importantly, how can I tie that number back to a connection that I've
>> acquired via JDBC?
>
> At a guess, it's the ephemeral port number used by the client
> connection.  It might be hard to track back in Java because I don't
> think the JDBC driver gives you access to the underlying Socket object
> (which you could query to find out its local port).

See the lsof unix tool for a good way to track which processes are
communicating via that port number.

Erik Jones

DBA | Emma®
erik@myemma.com
800.595.4401 or 615.292.5888
615.292.0777 (fax)

Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Function problem
Next
From: Enrico
Date:
Subject: Re: Function problem