> On Tue, Apr 13, 2021 at 5:51 PM Tatsuo Ishii <ishii@sraoss.co.jp> wrote:
>> Currently standard pgbench scenario produces transaction serialize
>> errors "could not serialize access due to concurrent update" if
>> PostgreSQL runs in REPEATABLE READ or SERIALIZABLE level, and the
>> session aborts. In order to achieve meaningful results even in these
>> transaction isolation levels, I would like to propose an automatic
>> retry feature if "could not serialize access due to concurrent update"
>> error occurs.
>>
>> Probably just adding a switch to retry is not enough, maybe retry
>> method (random interval etc.) and max retry number are needed to be
>> added.
>>
>> I would like to hear your thoughts,
>
> See also:
>
> https://www.postgresql.org/message-id/flat/72a0d590d6ba06f242d75c2e641820ec%40postgrespro.ru
Thanks for the pointer. It seems we need to resume the discussion.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
