diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-29 13:58:30 -0500 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-11-29 13:58:30 -0500 |
commit | d5e2bdf7dda712a60234f08e036ec9de28085a2d (patch) | |
tree | c3a49d2769cedd273e810416f8ab9a7aea85220a /src/backend/tcop/postgres.c | |
parent | 0f89ca083bbf71641cf61b4b951d6b30a2fd978b (diff) | |
download | postgresql-d5e2bdf7dda712a60234f08e036ec9de28085a2d.tar.gz postgresql-d5e2bdf7dda712a60234f08e036ec9de28085a2d.zip |
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
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions