Re: enabling tcpip_socket by default - Mailing list pgsql-hackers

From Greg Stark
Subject Re: enabling tcpip_socket by default
Date
Msg-id 873c5yvhy4.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: enabling tcpip_socket by default  (Doug McNaught <doug@mcnaught.org>)
Responses Re: enabling tcpip_socket by default  (Doug McNaught <doug@mcnaught.org>)
List pgsql-hackers
Doug McNaught <doug@mcnaught.org> writes:

> Greg Stark <gsstark@mit.edu> writes:
> 
> > Marko Karppinen <marko@karppinen.fi> writes:
> >
> >> On 17. touko 2004, at 10:40, Tatsuo Ishii wrote:
> >> > Consider a program using JDBC on localhost. It can only reach to
> >> > PostgreSQL via TCP/IP.
> >
> > Huh? Why on earth would that be true? Is this a limitation of our JDBC
> > drivers?
> 
> Java doesn't support Unix domain sockets.  If you want to use JDBC,
> you have to use TCP sockets.

That doesn't follow. That just means you can't implement a unix domain socket
driver using only Java. Is there some reason the driver has to be pure a Java
driver?

I had always assumed the JDBC driver isn't currently pure java and is just an
API wrapper around libpq. Writing and maintaining a pure java driver would be
much more work and be much slower for no practical gain.

-- 
greg



pgsql-hackers by date:

Previous
From: Doug McNaught
Date:
Subject: Re: enabling tcpip_socket by default
Next
From: Andrew Dunstan
Date:
Subject: Re: enabling tcpip_socket by default