| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | depesz(at)depesz(dot)com |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: psql doesn't reuse -p after backend fail |
| Date: | 2011-09-06 15:35:43 |
| Message-ID: | 7375.1315323343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | hubert depesz lubaczewski | 2011-09-06 15:38:29 | Re: psql doesn't reuse -p after backend fail |
| Previous Message | hubert depesz lubaczewski | 2011-09-06 15:12:54 | Re: psql doesn't reuse -p after backend fail |