From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Ramon Danieli" <ramond(at)post(dot)tau(dot)ac(dot)il>, <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Unix domain socket |
Date: | 2005-02-24 08:13:36 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E472B6D8@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Ramon Danieli
> Sent: 23 February 2005 22:15
> To: pgsql-odbc(at)postgresql(dot)org
> Subject: Re: [ODBC] Unix domain socket
>
> While having another look in the sources (08.00.0004) I have
> found some code
> that seems to provide Unix domain sockets connection in socket.c.
> This code depends on "HAVE_UNIX_SOCKETS" macro and seems to
> allow a single hard
> coded path (/tmp/...) while providing an empty "ServerName"
> property in the
> connection string.
> Can you please explain the nature of this code (it was not
> available in the
> 07.03.0200 version)?
> What is required (configure, compilation flags, etc`) in
> order to have this
> macro valid (I think that normally this code is not included)?
> Why does it have a single hard coded path?
Hmm, did even realise it had crept in there. Well to enable it you will
need to define the HAVE_UNIX_SOCKETS macro when you compile. Does it
then work? As for why it's done the way it is, I have no idea - it was
committed by Hiroshi Inoue, so he'd need to answer that - unfortunately
though, he no longer works on psqlODBC.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-02-24 11:47:54 | Re: (Fwd) SQLSetPos problem under Linux |
Previous Message | lothar.behrens | 2005-02-24 06:22:30 | (Fwd) SQLSetPos problem under Linux |