On Sun, Dec 19, 2010 at 13:42, Greg Sabino Mullane <greg@turnstep.com> wrot=
e:
>
>> How much are the postgres people willing to find a solution that would
>> force postgres to optional use BSD type sockets?
>
> FWIW, my long-term plan is to have DBD::Pg provide its own libpq. Not
> sure if this would enable you to solve the problem or not, but
> I suspect it might. Actually removing the libpq dependency is awaiting
> copious amounts of free time on my part, or funding from a sponsor.
> But it's on the todo list. :)
Spinning off into the off-topic based on the question - if you do
this, please make it *optional*. Unless you plan to actually implement
all the libpq functionality and also shoulder the burden to release a
new version whenever a new version of libpq is out. Things like
kerberos/gssapi and cert authentication that actually work the same
way as others...
Might be worth looking at what the ODBC folks did though - they run
the actual protocol for the queries, but they use libipq for
connection setup and authentication (if found - they'll fallback on
doing simple auth etc if libpq isn't there)
--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/
