aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/commit_ts.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2021-03-23 14:27:50 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2021-03-23 14:27:50 -0400
commitc6eac71a88447d82d5f6d28b6bed2e9c6971d714 (patch)
tree8fbdc6933571d854035eb81044d62413e1267afb /src/backend/access/transam/commit_ts.c
parentd4791ac35cb1d7417ea3cff6cc604623463ef0ea (diff)
downloadpostgresql-c6eac71a88447d82d5f6d28b6bed2e9c6971d714.tar.gz
postgresql-c6eac71a88447d82d5f6d28b6bed2e9c6971d714.zip
Fix psql's \connect command some more.
Jasen Betts reported yet another unintended side effect of commit 85c54287a: reconnecting with "\c service=whatever" did not have the expected results. The reason is that starting from the output of PQconndefaults() effectively allows environment variables (such as PGPORT) to override entries in the service file, whereas the normal priority is the other way around. Not using PQconndefaults at all would require yet a third main code path in do_connect's parameter setup, so I don't really want to fix it that way. But we can have the logic effectively ignore all the default values for just a couple more lines of code. This patch doesn't change the behavior for "\c -reuse-previous=on service=whatever". That remains significantly different from before 85c54287a, because many more parameters will be re-used, and thus not be possible for service entries to replace. But I think this is (mostly?) intentional. In any case, since libpq does not report where it got parameter values from, it's hard to do differently. Per bug #16936 from Jasen Betts. As with the previous patches, back-patch to all supported branches. (9.5 is unfortunately now out of support, so this won't get fixed there.) Discussion: https://postgr.es/m/16936-3f524322a53a29f0@postgresql.org
Diffstat (limited to 'src/backend/access/transam/commit_ts.c')
0 files changed, 0 insertions, 0 deletions