Re: Another review of URI for libpq, v7 submission

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Alex <ash(at)commandprompt(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Another review of URI for libpq, v7 submission
Date: 2012-04-06 03:25:39
Message-ID: 1333681634-sup-8491@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Alvaro Herrera's message of jue abr 05 19:10:25 -0300 2012:

> I think the only thing I'm not really sure about is the usage of the
> <synopsis> tag to mark example URIs in the docs. It looks to me that
> they should mostly be <literal> instead, but I'm not really sure about
> that either -- I'm suspecting the PDF output would look rather horrible.

Some moments of radical thinking later, I became unhappy with the fact
that the conninfo stuff and parameter keywords are all crammed in the
PQconnectdbParams description. This feels wrong to me, even more so
after we expand it even more to add URIs to the mix. I think it's
better to create a separate sect1 (which I've entitled "Connection
Strings") which explains the conninfo and URI formats as well as
accepted keywords. The new section is referenced from the multiple
places that need it, without having to point to PQconnectdbParams.

Thoughts?

Wording suggestions are welcome.

dblink_connect docs should also have a mention of URIs now:

alvherre=# select dblink_connect('postgresql://localhost:55432');
dblink_connect
----------------
OK
(1 fila)

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment Content-Type Size
libpq-docs.patch application/octet-stream 49.1 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-04-06 04:30:05 Re: measuring lwlock-related latency spikes
Previous Message Shigeru HANADA 2012-04-06 02:41:29 Re: WIP: Collecting statistics on CSV file data