Doc: clarify behavior of PQconnectdbParams().

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 414fb255e55f249f2c5e6d207ef6bd98c460a730
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2020-11-29T18:58:30Z
Releases: 9.5.25
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

Files

PathChange+/−
doc/src/sgml/libpq.sgml modified +57 −44

Discussion