Re: psql doesn't reuse -p after backend fail - Mailing list pgsql-bugs

From hubert depesz lubaczewski
Subject Re: psql doesn't reuse -p after backend fail
Date
Msg-id 20110906151253.GA1209@depesz.com
Whole thread Raw
In response to Re: psql doesn't reuse -p after backend fail  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: psql doesn't reuse -p after backend fail  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: psql doesn't reuse -p after backend fail  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
On Mon, Sep 05, 2011 at 02:27:23PM -0400, Tom Lane wrote:
> It's not just the port, it's all the connection parameters ---
> do_connect relies on the PGconn object to remember those, and in this
> case there no longer is a PGconn object.
>
> We could have psql keep that information separately, but I'm not sure
> it's really worth the trouble.

well, I think it's definitely worth the trouble. If I had datbaase
standing at 5432, it would connect to it, and then I could mistakenly
ran commands to wrong database.
this is clearly not a good thing.

depesz

--
The best thing about modern society is how easy it is to avoid contact with it.
                                                             http://depesz.com/

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: BUG #5932: CLUSTER doesn't update n_dead_tup
Next
From: Tom Lane
Date:
Subject: Re: psql doesn't reuse -p after backend fail