On Nov 15, 2010, at 9:05 AM, Steve Clark wrote:
> netstat -an will do it on linux.
>
> sockstat will do it on FreeBSD.
>
> What's OS X ? ;-)
Apple must use very different option switches for their netstat, because I see
no way to get PIDs (which seems like a pretty big oversight to me), and -
On Nov 15, 2010, at 9:24 AM, Tom Lane wrote:
> In that case see lsof --- you can match up the ends of the connection
> using the hex value in the "device" column.
>
> regards, tom lane
>
Yes, that works. Match "Address" from netstat to "DEVICE" in lsof.
Thanks.
--
Sco
Scott Ribe writes:
> On Nov 15, 2010, at 8:50 AM, Tom Lane wrote:
>> netstat will probably work for this, depending on what platform you're on.
> OS X. I can see the connections, but I don't see an option to display PIDs.
In that case see lsof --- you can match up the ends of the connection
usin
On 11/15/2010 11:00 AM, Scott Ribe wrote:
On Nov 15, 2010, at 8:50 AM, Tom Lane wrote:
netstat will probably work for this, depending on what platform you're on.
OS X. I can see the connections, but I don't see an option to display PIDs.
netstat -an will do it on linux.
sockst
On Nov 15, 2010, at 8:50 AM, Tom Lane wrote:
> netstat will probably work for this, depending on what platform you're on.
OS X. I can see the connections, but I don't see an option to display PIDs.
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
Scott Ribe writes:
> Assume I have a local process which leaves a transaction open & idle for an
> extended period of time. Is there any way to identify the local process
> connected to a particular backend?
netstat will probably work for this, depending on what platform you're on.
Assume I have a local process which leaves a transaction open & idle for an
extended period of time. Is there any way to identify the local process
connected to a particular backend?
pg_stat_activity is fine for TCP connections but does not provide useful
identifying information for domain sock
