From: | Alexander Shulgin <ash(at)commandprompt(dot)com> |
---|---|
To: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Notes on implementing URI syntax for libpq |
Date: | 2011-11-24 07:24:42 |
Message-ID: | 1322119250-sup-6088@moon |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Dmitriy Igrishin's message of Thu Nov 24 09:19:02 +0200 2011:
>
> > If host part of the URI points to localhost, the UNIX domain socket would
> > be considered by libpq just as if you would pass "-h localhost -p 5433".
> >
> But what if the user wants to connect exactly via socket or
> TCP/IP ?
> And what if the user needs to specify a socket file name extension?
How do you achieve that with the current psql set of command line options (and, possibly environment variables?)
I would think the same method will work with URI, as with the proposed approach the URI is just decomposed into host, port and dbname parts and the rest of the code works like if you've had specified "-h example.net -p 5433 -d mydb" instead of the URI parameter.
--
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2011-11-24 07:40:42 | Re: Notes on implementing URI syntax for libpq |
Previous Message | Dmitriy Igrishin | 2011-11-24 07:19:02 | Re: Notes on implementing URI syntax for libpq |