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 | 5fe3e9333287c33da710ace62648df4531e5f307 (patch) | |
tree | e2b9be15dc65f6828a67aedf703f6ea17557cb42 /src/backend/parser/parse_target.c | |
parent | 40f2fbe71ad615a2bcaaf5b840ccb9329e4378aa (diff) | |
download | postgresql-5fe3e9333287c33da710ace62648df4531e5f307.tar.gz postgresql-5fe3e9333287c33da710ace62648df4531e5f307.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/parser/parse_target.c')
0 files changed, 0 insertions, 0 deletions