Re: Mop-up around psql's \connect behavior
Chapman Flack <chap@anastigmatix.net>
From: Chapman Flack <chap@anastigmatix.net>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2020-10-21T23:04:49Z
Lists: pgsql-hackers
On 10/21/20 18:59, Tom Lane wrote: > I think the reason we've not had complaints about this is that the > situation normally doesn't arise in interactive sessions (since we > won't release the old connection voluntarily), while scripts are > likely not designed to cope with connection losses anyway. These > facts militate against spending a whole lot of effort on a fix, > but still we ought to reduce the silliness factor. What I propose > is to complain if we have no o_conn *and* we are asked to re-use > parameters from it. Otherwise, it's fine. I've been getting around it just by saying \c "connstring" . . . which works. It gives me a tiny thrill every time I do it, like I'm getting away with something. Which is why I haven't been complaining. I suppose I wouldn't complain if it were fixed, either. Regards, -Chap
Commits
-
Allow psql to re-use connection parameters after a connection loss.
- 1b62d0fb3e50 14.0 landed
-
Clean up some unpleasant behaviors in psql's \connect command.
- 94929f1cf6cb 14.0 landed
-
Fix connection string handling in psql's \connect command.
- 85c54287af56 14.0 cited