| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Oleksandr Shulgin <oleksandr(dot)shulgin(at)zalando(dot)de>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Danger of automatic connection reset in psql |
| Date: | 2016-11-11 04:14:52 |
| Message-ID: | CAFjFpReDYr2PnPY3fOfaXcrAxGyGTryw_GqzMn5GGY2FvD23bA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> How about, instead of all this, adding an option to psql to suppress
> the automatic reconnect behavior? When enabled, psql just exits
> instead of trying to reconnect.
>
+1. But, existing users may not notice addition of the new option and
still continue to face problem. If we add the option and make it
default not to reconnect, they will notice it and use option to get
older behaviour, but that will break applications relying on the
current behaviour. Either way, users will have at least something to
control the connection reset.
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | leoaaryan | 2016-11-11 04:26:10 | Re: Shared memory estimation for postgres |
| Previous Message | Craig Ringer | 2016-11-11 03:53:21 | Re: Shared memory estimation for postgres |