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 | bc3b4c8ca1524b46204a380619e4c778ff5eb7cb (patch) | |
tree | fed9a3302922519296e4154c52dfa981050e5cee /src/backend/executor/nodeWindowAgg.c | |
parent | f6324bbbe63c5430eee1ffc3cf56fc56ab2c1af8 (diff) |
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/executor/nodeWindowAgg.c')
0 files changed, 0 insertions, 0 deletions