Re: Notes on implementing URI syntax for libpq

From: Greg Smith <greg(at)2ndQuadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Notes on implementing URI syntax for libpq
Date: 2011-11-28 08:08:42
Message-ID: 4ED3418A.2010601@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/24/2011 05:21 AM, Alvaro Herrera wrote:
> A coworker also suggested using a different designator:
>
> postgresqli:///path/to/socket:5433/database
> postgresqli://:5433/database

This is not unprecedented. An example is how CUPS handles this problem
when connecting printers using URIs:
http://www.cups.org/documentation.php/network.html where you might see
this for the usual port:

lpd://ip-address-or-hostname/queue

And this for AppSocket AKA JetDirect:

socket://ip-address-or-hostname

I am certainly not going to defend printing setup with CUPS as a model
worth emulating, just noting the similarity here. I think we'll save
miles of user headaches if there's only one designator.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Smith 2011-11-28 08:53:01 Re: Displaying accumulated autovacuum cost
Previous Message Greg Smith 2011-11-28 07:54:38 Re: Patch: add timing of buffer I/O requests