Re: listening on tcp socket instead of unix domain - Mailing list pgsql-admin

From Tom Lane
Subject Re: listening on tcp socket instead of unix domain
Date
Msg-id 28987.1119728982@sss.pgh.pa.us
Whole thread Raw
In response to listening on tcp socket instead of unix domain  (David Bear <David.Bear@asu.edu>)
Responses wal logs in pg_xlog  (Nasir Iqbal Danish <nasir@amaana.com>)
List pgsql-admin
David Bear <David.Bear@asu.edu> writes:
> However, a netstat -l tells me:

> netstat -l | grep 5432
> unix  2      [ ACC ]     STREAM     LISTENING     732094 /tmp/.s.PGSQL.5432

> netstat -l | grep postg
> tcp        0      0 localhost:postgresql    *:* LISTEN
> tcp        0      0 localhost:postgresql    *:* LISTEN

> This doesn't look right.

It looks fine to me.  The reason there are two listening sockets is most
likely that one is IPv4 and the other is IPv6 --- netstat's default display
fails to distinguish this (at least on Linux), but you can see it if you
do "netstat -l -n".

> Moreover, when attempting to create an ssh tunnel to connect to
> postgres from a windows box, the connection fails.

You're going to have to give more detail (like exactly what you tried
and exactly what happened) if you want help with that.  It could be a
firewall issue, but that's strictly a guess.

            regards, tom lane

pgsql-admin by date:

Previous
From: David Bear
Date:
Subject: listening on tcp socket instead of unix domain
Next
From: Alberto
Date:
Subject: Re: pg_dump -Fc does not dump indexes