Re: idle-in-transaction timeout error does not give a hint - Mailing list pgsql-hackers

From Tatsuo Ishii
Subject Re: idle-in-transaction timeout error does not give a hint
Date
Msg-id 20181129.091601.830026250066724330.t-ishii@sraoss.co.jp
Whole thread Raw
In response to RE: idle-in-transaction timeout error does not give a hint  ("Ideriha, Takeshi" <ideriha.takeshi@jp.fujitsu.com>)
Responses Re: idle-in-transaction timeout error does not give a hint
Re: idle-in-transaction timeout error does not give a hint
List 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.
> 
> Agreed. Changing "command" to "transaction" seems more accurate. People might think
> only the command they hit is not sent but transaction is still alive though it's of course unnatural
> that transaction is alive after connection is terminated.
> 
> In this case you could change the comment issued by other errors mentioned while you're at it.
> 
> Regards,
> Takeshi Ideriha

I have added this to the next CF (2019-01).

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: COPY FROM WHEN condition
Next
From: Michael Paquier
Date:
Subject: Re: A WalSnd issue related to state WALSNDSTATE_STOPPING