| From: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | ideriha(dot)takeshi(at)jp(dot)fujitsu(dot)com |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: idle-in-transaction timeout error does not give a hint |
| Date: | 2018-11-28 09:06:17 |
| Message-ID: | 20181128.180617.1161250201215005974.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hi, it makes sense to me. One can submit transaction again same as other cases
> you mentioned.
>
> I didn't attach the patch but according to my simple experiment
> in psql the output would become the following:
>
> FATAL: terminating connection due to idle-in-transaction timeout
> HINT: In a moment you should be able to reconnect to the
> database and repeat your command.
Alternative HINT message would be something like:
HINT: In a moment you should be able to reconnect to the
database and restart your transaction.
This could make the meaning of the error (transaction aborted)
cleaner and might give a better suggestion to the user.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2018-11-28 09:34:41 | Re: "pg_ctl: the PID file ... is empty" at end of make check |
| Previous Message | Lætitia Avrot | 2018-11-28 08:59:08 | Markdown format output for psql, design notes |