Doc: clarify behavior of PQconnectdbParams().
authorTom Lane <[email protected]>
Sun, 29 Nov 2020 18:58:30 +0000 (13:58 -0500)
committerTom Lane <[email protected]>
Sun, 29 Nov 2020 18:58:30 +0000 (13:58 -0500)
commit414fb255e55f249f2c5e6d207ef6bd98c460a730
tree85448aa0b22e980c3369e5eb57087d1d676f4610
parent60d6c71430f9f95021f8da5064d5aa47015f7575
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
doc/src/sgml/libpq.sgml