| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | amul sul <sul_amul(at)yahoo(dot)co(dot)in> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal to add connection request Wait-time in PSQL client. |
| Date: | 2013-05-19 03:54:41 |
| Message-ID: | 51984D01.6020103@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/19/2013 11:41 AM, amul sul wrote:
> in a way, we client terminal wont hangup by throwing *The connection to the server was lost. Attempting reset: Failed. !*
The thing is that this just should not be a routine occurrence. It's a
minor irritation to me when debugging sometimes, but it's not something
that you should be encountering in production. If you are, changing
psql's reconnect behaviour is not necessarily the best solution. I'd try
to work out why you're having so many unrecoverable disconnects and
restarts and fix that instead.
Making psql smarter about reconnecting to solve server crashes feels a
bit like carrying a bunch of spare fuel cans in the back of a car for
when you run out of fuel. It's not necessarily a terrible idea, but you
should really never need it either.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Soroosh Sardari | 2013-05-19 06:07:23 | Re: Road map to study about fetching a set of tuples - novice! |
| Previous Message | amul sul | 2013-05-19 03:41:39 | Re: Proposal to add connection request Wait-time in PSQL client. |