|From:||Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>|
|Subject:||Re: idle-in-transaction timeout error does not give a hint|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
>>From: Tatsuo Ishii [mailto:ishii(at)sraoss(dot)co(dot)jp]
>>> 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.
>>Hum. Sounds like a fair argument. Ideriha-san, what do you think?
> As Peter mentioned, application code generally needs to handle more things
> than retrying.
> So I'm ok with not adding this hint.
I have changed the patch status to "Withdrawn".
SRA OSS, Inc. Japan
|Next Message||David Rowley||2019-04-01 00:24:56||Re: speeding up planning with partitions|
|Previous Message||Ideriha, Takeshi||2019-03-31 23:44:23||RE: idle-in-transaction timeout error does not give a hint|