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

From Peter Eisentraut
Subject Re: psql doesn't reuse -p after backend fail
Date
Msg-id 1315476562.17143.0.camel@fsopti579.F-Secure.com
Whole thread Raw
In response to Re: psql doesn't reuse -p after backend fail  (hubert depesz lubaczewski <depesz@depesz.com>)
Responses Re: psql doesn't reuse -p after backend fail  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On tis, 2011-09-06 at 17:12 +0200, hubert depesz lubaczewski wrote:
> 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.

Perhaps just prevent \connect without argument if the information is no
longer available.

pgsql-bugs by date:

Previous
From: John R Pierce
Date:
Subject: Re: In Windows Server 2008 PostgreSQL8.3 service on Local Computer started and then stopped.
Next
From: "Daniel Farina"
Date:
Subject: BUG #6200: standby bad memory allocations on SELECT