Re: BUG #16746: [PG12.5 psql] Password ignored by connect meta-command
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: kgradekx@gmail.com,
PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2020-11-29T02:59:06Z
Lists: pgsql-bugs
Attachments
- fix-PQconnectdbParams-docs.patch (text/x-diff) patch
I wrote: > Ugh... looks like I broke this in 85c54287a et al. I had thought that > this was the pre-existing behavior, but after further study I see that > I was mistaken about how PQconnectdbParams() handles parameter > replacement, so I misread what the prior code was really doing. While I take full responsibility for having messed up here, I note that the documentation for PQconnectdbParams is seriously misleading on the point, in that it fails to point out that parameters appearing after "dbname" will only override the connstring if they supply non-empty values. Besides that, it's rather in need of copy-editing, not to mention some minimal thought about what is a reasonable order to make its points in. So I propose the attached docs fix to begin with. regards, tom lane
Commits
-
Fix recently-introduced breakage in psql's \connect command.
- e2d5de15003d 9.5.25 landed
- 946277fd42d4 10.16 landed
- 7e5e1bba034e 14.0 landed
- 777ac03a6823 11.11 landed
- 72b930f5045e 13.2 landed
- 3f59a05f0fa8 9.6.21 landed
- 3958abdad337 12.6 landed
-
Doc: clarify behavior of PQconnectdbParams().
- db83c0450929 12.6 landed
- d5e2bdf7dda7 14.0 landed
- bc3b4c8ca152 10.16 landed
- 7fbd1442807a 9.6.21 landed
- 5fe3e9333287 11.11 landed
- 414fb255e55f 9.5.25 landed
- 1eb499a8a5e6 13.2 landed
-
Allow psql to re-use connection parameters after a connection loss.
- 1b62d0fb3e50 14.0 cited
-
Clean up some unpleasant behaviors in psql's \connect command.
- 94929f1cf6cb 14.0 cited
-
Fix connection string handling in psql's \connect command.
- 85c54287af56 14.0 cited