From: Tom Lane <tgl@sss.pgh.pa.us>
To: David.Bear@asu.edu
Cc: pgsql-admin@postgresql.org
Subject: Re: listening on tcp socket instead of unix domain
Date: Sat, 25 Jun 2005 15:49:42 -0400
Message-ID: <28987.1119728982@sss.pgh.pa.us> (raw)
In-Reply-To: <20050625175849.GA18646@asu.edu>
References: <20050625175849.GA18646@asu.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, David.Bear@asu.edu
Subject: Re: listening on tcp socket instead of unix domain
In-Reply-To: <28987.1119728982@sss.pgh.pa.us>
References: <20050625175849.GA18646@asu.edu> <28987.1119728982@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox