| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: idle-in-transaction timeout error does not give a hint |
| Date: | 2019-03-28 09:06:55 |
| Message-ID: | 0f5a126b-e779-d368-b2c8-a3514ebc65af@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018-11-28 04:17, Tatsuo Ishii wrote:
> + errmsg("terminating connection due to idle-in-transaction timeout"),
> + errhint("In a moment you should be able to reconnect to the"
> + " database and repeat your command.")));
Personally, I don't find this hint particularly necessary. The session
was terminated because nothing was happening, so the real fix on the
application side is probably more involved than just retrying. This is
different from some of the other cases that were cited, such as
serialization conflicts, where you just got unlucky due to concurrent
events. In the case of idle-in-transaction-timeout, the fault is
entirely your own.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-03-28 09:08:36 | Re: Progress reporting for pg_verify_checksums |
| Previous Message | Darafei Komяpa Praliaskouski | 2019-03-28 09:03:47 | Re: Berserk Autovacuum (let's save next Mandrill) |