By no-networking I meant using --tcip_socket=false. I think this was
accurate. When you run postgres with this option and use unix domain sockets
and connect with psql or pgAdmin, you are connecting to a postgres server
without networking. These work under cygwin, but not from a Java client.
"UNIX domain sockets communicate only between processes on a single host.
Sockets in the UNIX domain are not considered part of the network protocols
because they can be used to communicate only between processes on a single
host."
I guess I brought the vocabulary from MySQL were you use "skip networking"
and the server allows you to connect on the local machine with named pipes,
even with JDBC.
Chris
-----Original Message-----
From: Peter Eisentraut [mailto:peter_e@gmx.net]
Sent: 23 September 2003 20:58
To: Chris Faulkner
Cc: pgsql-cygwin@postgresql.org; pgsql-jdbc@postgresql.org
Subject: Re: [CYGWIN] authentication
Chris Faulkner writes:
> I am using postgres in the cygwin environment. I have two services set
up -
> one launches it with no networking and one with networking so that it runs
> on port 5432.
You're going to have a pretty hard time connecting to a PostgreSQL server
without networking. Or what is your definition of no networking?
> # TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
> local all all
password
> WHatever change I make to this, psql never prompts when running on the
same
> machine.
Perhaps you're not connecting through a Unix-domain socket, but instead
via TCP/IP?
--
Peter Eisentraut peter_e@gmx.net
