Re: WIP: URI connection string support for libpq - Mailing list pgsql-hackers

From Florian Weimer
Subject Re: WIP: URI connection string support for libpq
Date
Msg-id 82k43cz8fq.fsf@mid.bfk.de
Whole thread Raw
In response to Re: WIP: URI connection string support for libpq  (Alex Shulgin <ash@commandprompt.com>)
Responses Re: WIP: URI connection string support for libpq
List pgsql-hackers
* Alex Shulgin:

> Yeah, this is really appealing, however how do you tell if the part
> after the last slash is a socket directory name or a dbname?  E.g:
>
> psql postgres:///path/to/different/socket/dir        (default dbname)
> psql postgres:///path/to/different/socket/dir/other  (dbname=other ?)

The HTTP precent is to probe the file system until you find something.
Most HTTP servers have something similar to the PATH_INFO variable which
captures trailing path segments.

It's ugly, but it's standard practice, and seems better than a separate
-d parameter (which sort of defeats the purpose of URIs).

--
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99


pgsql-hackers by date:

Previous
From: Alex Shulgin
Date:
Subject: Re: WIP: URI connection string support for libpq
Next
From: Alex Shulgin
Date:
Subject: Re: WIP: URI connection string support for libpq