| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | pgsql: Doc: clarify behavior of PQconnectdbParams(). |
| Date: | 2020-11-29 18:58:57 |
| Message-ID: | E1kjRuT-0003WA-Ds@gemulon.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Doc: clarify behavior of PQconnectdbParams().
The documentation omitted the critical tidbit that a keyword-array entry
is simply ignored if its corresponding value-array entry is NULL or an
empty string; it will *not* override any previously-obtained value for
the parameter. (See conninfo_array_parse().) I'd supposed that would
force the setting back to default, which is what led me into bug #16746;
but it doesn't.
While here, I couldn't resist the temptation to do some copy-editing,
both in the description of PQconnectdbParams() and in the section
about connection URI syntax.
Discussion: https://postgr.es/m/931505.1606618746@sss.pgh.pa.us
Branch
------
REL9_6_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/7fbd1442807ad62ee0e71e2ff3f8b0eefb0af5b8
Modified Files
--------------
doc/src/sgml/libpq.sgml | 101 +++++++++++++++++++++++++++---------------------
1 file changed, 57 insertions(+), 44 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-11-29 20:22:27 | pgsql: Fix recently-introduced breakage in psql's \connect command. |
| Previous Message | Noah Misch | 2020-11-29 05:54:16 | pgsql: Retry initial slurp_file("current_logfiles"), in test 004_logrot |