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:38:29
Message-ID: 20110906153828.GA16610@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 06, 2011 at 11:35:43AM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > 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.
>
> [ shrug.. ] So submit a patch. Personally I don't think the case comes

way above my skillset :(

> up often enough to be worth the trouble, and I'd much rather spend
> development time on preventing the server from crashing in the first
> place.

the reason for the crash is discussed in the pg_upgrade thread on
hackers. ( 8.3 ltree + pg_upgrade to 9.0.5 == backend crash on select).

Best regards,

depesz

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2011-09-06 15:49:48 Re: psql doesn't reuse -p after backend fail
Previous Message Tom Lane 2011-09-06 15:35:43 Re: psql doesn't reuse -p after backend fail