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 | 1eb499a8a5e6aa06f5bd8d53f2119e74efdd3db7 (patch) | |
| tree | 6bfeefc8ad41920384843b19494d90606181bd79 /src/backend/executor/nodeSort.c | |
| parent | 9a02dbdd03e8eadbe5331311c122548fac156f56 (diff) | |
| download | postgresql-1eb499a8a5e6aa06f5bd8d53f2119e74efdd3db7.tar.gz postgresql-1eb499a8a5e6aa06f5bd8d53f2119e74efdd3db7.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/executor/nodeSort.c')
0 files changed, 0 insertions, 0 deletions