Re: revisiting unix domain sockets
От | Charles Pritchard |
---|---|
Тема | Re: revisiting unix domain sockets |
Дата | |
Msg-id | 52DDB69D.1000008@jumis.com обсуждение исходный текст |
Ответ на | Re: revisiting unix domain sockets (Dave Cramer <pg@fastcrypt.com>) |
Ответы |
Re: revisiting unix domain sockets
|
Список | pgsql-jdbc |
Here's a quick diff if anyone is interested.
https://gist.github.com/Downchuck/8531692
Needs JNA in the class path. Seems to work.
We've released this under the same license as pgjdbc.
https://github.com/pgjdbc/pgjdbc/blob/master/LICENSE
Uses ?unixSocket= as the parameter for the path.
-Charles
On 12/17/2013 4:25 AM, Dave Cramer wrote:
https://gist.github.com/Downchuck/8531692
Needs JNA in the class path. Seems to work.
We've released this under the same license as pgjdbc.
https://github.com/pgjdbc/pgjdbc/blob/master/LICENSE
Uses ?unixSocket= as the parameter for the path.
-Charles
On 12/17/2013 4:25 AM, Dave Cramer wrote:
Send a PR and I'll look at it.On Tue, Dec 17, 2013 at 6:01 AM, Charles Pritchard <chuck@jumis.com> wrote:Has there been any movement and-or push back around supporting unix domain sockets within the connection string? I've seen simple patches on the web to add support- it seems like a trivial matter, is there a design consideration or other issue outstanding?
Example of using JNA for unix domain sockets:
http://www.productivity.org/projects/mysqlunixsocket/MysqlUnixSocketFactory.java
-Charles
--
Sent via pgsql-jdbc mailing list (pgsql-jdbc@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-jdbc
В списке pgsql-jdbc по дате отправления: