Re: Mop-up around psql's \connect behavior - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: Mop-up around psql's \connect behavior
Date
Msg-id 5F90BE91.5030306@anastigmatix.net
Whole thread Raw
In response to Mop-up around psql's \connect behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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



pgsql-hackers by date:

Previous
From: Anastasia Lubennikova
Date:
Subject: Re: Allow some recovery parameters to be changed with reload
Next
From: Peter Smith
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions