X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 358905280C for ; Sat, 25 Jun 2005 16:49:49 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71799-06 for ; Sat, 25 Jun 2005 19:49:43 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 8A2215288D for ; Sat, 25 Jun 2005 16:49:42 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id j5PJngSY028988; Sat, 25 Jun 2005 15:49:42 -0400 (EDT) To: David.Bear@asu.edu Cc: pgsql-admin@postgresql.org Subject: Re: listening on tcp socket instead of unix domain In-reply-to: <20050625175849.GA18646@asu.edu> References: <20050625175849.GA18646@asu.edu> Comments: In-reply-to David Bear message dated "Sat, 25 Jun 2005 10:58:49 -0700" Date: Sat, 25 Jun 2005 15:49:42 -0400 Message-ID: <28987.1119728982@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/215 X-Sequence-Number: 17970 David Bear 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