Skip site navigation (1) Skip section navigation (2)

Re: listening on tcp socket instead of unix domain

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David(dot)Bear(at)asu(dot)edu
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: listening on tcp socket instead of unix domain
Date: 2005-06-25 19:49:42
Message-ID: 28987.1119728982@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
David Bear <David(dot)Bear(at)asu(dot)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

In response to

Responses

pgsql-admin by date

Next:From: AlbertoDate: 2005-06-25 20:39:41
Subject: Re: pg_dump -Fc does not dump indexes
Previous:From: Marek Aleksander DÄ…bekDate: 2005-06-25 18:44:03
Subject: Windows XP installation problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group