From: | Dmitriy Igrishin <dmitigr(at)gmail(dot)com> |
---|---|
To: | Alexander Shulgin <ash(at)commandprompt(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:19:02 |
Message-ID: | CAAfz9KOLCu3usK+xWQjK1ZfiP5+FxYSGLemK3Wy_wZjn_KX4kQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey Alexander,
2011/11/24 Alexander Shulgin <ash(at)commandprompt(dot)com>
>
> Excerpts from Florian Weimer's message of Wed Nov 23 13:04:47 +0200 2011:
> >
> > * Alexander Shulgin:
> >
> > > 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?
>
> Missed that in my previous reply.
>
> 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?
--
// Dmitriy.
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Shulgin | 2011-11-24 07:24:42 | Re: Notes on implementing URI syntax for libpq |
Previous Message | Alexander Shulgin | 2011-11-24 06:59:56 | Re: Notes on implementing URI syntax for libpq |