From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Danger of automatic connection reset in psql |
Date: | 2016-11-15 15:10:53 |
Message-ID: | 6c247899-076f-803e-4d07-6a7f57ad8ae0@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/14/16 5:41 AM, Oleksandr Shulgin wrote:
> Automatic connection reset is a nice feature for server development,
> IMO. Is it really useful for anything else is a good question.
I use it all the time for application development; my rebuild script
will forcibly kick everyone out to re-create the database. I put that in
because I invariably end up with a random psql sitting somewhere that I
don't want to track down.
What currently stinks though is if the connection is dead and the next
command I run is a \i, psql just dies instead of re-connecting. It'd be
nice if before reading the script it checked connection status and
attempted a reconnect.
> At least an option to control that behavior seems like a good idea,
> maybe even set it to 'no reconnect' by default, so that people who
> really use it can make conscious choice about enabling it in their
> .psqlrc or elsewhere.
+1, I don't think it needs to be the default.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2016-11-15 15:41:18 | Parallel execution and prepared statements |
Previous Message | Magnus Hagander | 2016-11-15 14:58:48 | Re: Physical append-only tables |