On Tue, Dec 04, 2018 at 04:07:34AM +, Ideriha, Takeshi wrote:
> Sure. I didn't have a strong opinion about it, so it's ok.
From what I can see this is waiting input from a native English
speaker, so for now I have moved this entry to next CF.
--
Michael
signature.asc
Description: PGP signatu
>From: Tatsuo Ishii [mailto:is...@sraoss.co.jp]
>Subject: Re: idle-in-transaction timeout error does not give a hint
>
>>>>>>Alternative HINT message would be something like:
>>>>>>
>>>>>>HINT: In a moment you should be able to rec
>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 t
t 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
>>>>
ned.
>> >>>
>> >>> 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
>&
>> 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 t
me 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 woul
>>> 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:
>>>
>>&g
>> 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: terminatin
> 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-tran
>From: Tatsuo Ishii [mailto:is...@sraoss.co.jp]
>Sent: Wednesday, November 28, 2018 12:18 PM
>To: pgsql-hackers@lists.postgresql.org
>Subject: idle-in-transaction timeout error does not give a hint
>
>idle-in-transaction timeout error closed the session. I think in this case th
idle-in-transaction timeout error closed the session. I think in this
case the error message should give a hint something like other errors
(for example ERRCODE_CRASH_SHUTDOWN or
ERRCODE_T_R_SERIALIZATION_FAILURE) to ask users to reconnect.
Attached patch does that.
Best regards,
--
Tatsuo Ishii
101 - 112 of 112 matches
Mail list logo