Skip site navigation (1) Skip section navigation (2)

Re: psql doesn't reuse -p after backend fail

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: psql doesn't reuse -p after backend fail
Date: 2011-09-06 15:12:54
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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.


The best thing about modern society is how easy it is to avoid contact with it.

In response to


pgsql-bugs by date

Next:From: Tom LaneDate: 2011-09-06 15:35:43
Subject: Re: psql doesn't reuse -p after backend fail
Previous:From: Bruce MomjianDate: 2011-09-06 14:08:59
Subject: Re: BUG #5932: CLUSTER doesn't update n_dead_tup

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group