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 | db83c0450929f89b293ae30a8d68d520a91b7ead (patch) | |
| tree | af236405c7fcf6f98f6f3642f2f1a9f9e00982a5 /src/backend/parser/parse_utilcmd.c | |
| parent | 7b5b90be95663f3feb1f7c141b07485d593268cf (diff) | |
| download | postgresql-db83c0450929f89b293ae30a8d68d520a91b7ead.tar.gz postgresql-db83c0450929f89b293ae30a8d68d520a91b7ead.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_utilcmd.c')
0 files changed, 0 insertions, 0 deletions