| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: psql doesn't reuse -p after backend fail |
| Date: | 2011-09-08 10:09:22 |
| Message-ID: | 1315476562.17143.0.camel@fsopti579.F-Secure.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Farina | 2011-09-08 22:33:37 | BUG #6200: standby bad memory allocations on SELECT |
| Previous Message | John R Pierce | 2011-09-07 19:02:07 | Re: In Windows Server 2008 PostgreSQL8.3 service on Local Computer started and then stopped. |