pgsql: Doc: clarify behavior of PQconnectdbParams().

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-0003Vy-Bt@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
------
REL_13_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/1eb499a8a5e6aa06f5bd8d53f2119e74efdd3db7

Modified Files
--------------
doc/src/sgml/libpq.sgml | 96 +++++++++++++++++++++++++++----------------------
1 file changed, 54 insertions(+), 42 deletions(-)

Browse pgsql-committers by date

  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