Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.1/8.9.1) with ESMTP id RAA28309
	for <pgsql-interfaces@postgreSQL.org>;
	Sat, 16 Jan 1999 17:33:13 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id RAA26428;
	Sat, 16 Jan 1999 17:32:02 -0500 (EST)
To: Jonathan Sand <sand@gizmolab.com>
cc: "postgres jdbc" <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] can't connect via jdbc 
In-reply-to: Your message of Sat, 16 Jan 99 13:43:24 -0800
	<199901162143.NAA28321@scruz.net>
Date: Sat, 16 Jan 1999 17:32:02 -0500
Message-ID: <26426.916525922@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Jonathan Sand <sand@gizmolab.com> writes:
> If some kind soul could help straighten me out... :)

> su postgres -c '/usr/bin/postmaster -d 9 -p 2002 -D/var/lib/pgsql > 
> /var/lib/pgsql/log/pg_log 2>&1 &'

You forgot the -i switch ... so the postmaster is not listening for TCP
connections, only local Unix-socket connections.

Note to postgres crew: I think we ought to think about changing the
postmaster switches so that -i is default behavior, and you have to
supply some other switch if you want to *turn off* TCP access.  This
Question is far too Frequently Asked...

			regards, tom lane