Re: Notes on implementing URI syntax for libpq
От | Dmitriy Igrishin |
---|---|
Тема | Re: Notes on implementing URI syntax for libpq |
Дата | |
Msg-id | CAAfz9KOLCu3usK+xWQjK1ZfiP5+FxYSGLemK3Wy_wZjn_KX4kQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Notes on implementing URI syntax for libpq (Alexander Shulgin <ash@commandprompt.com>) |
Ответы |
Re: Notes on implementing URI syntax for libpq
|
Список | pgsql-hackers |
Hey Alexander,
// Dmitriy.
2011/11/24 Alexander Shulgin <ash@commandprompt.com>
--
Excerpts from Florian Weimer's message of Wed Nov 23 13:04:47 +0200 2011:
>> * Alexander Shulgin:Missed that in my previous reply.
>
> > This, in my opinion, is very similar to what we would like to achieve with the URI syntax, so the above could also be specified using a URI parameter like this:
> >
> > psql -d postgresql://example.net:5433/mydb
>
> How would you specifiy a local port/UNIX domain socket?
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?
TCP/IP ?
And what if the user needs to specify a socket file name extension?
// Dmitriy.
В списке pgsql-hackers по дате отправления: