| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Retry in pgbench |
| Date: | 2021-04-13 07:02:20 |
| Message-ID: | CA+hUKGLL2+BCErRbrHTgw+4BB6x+V9d4a4uhZYc1yBRw+59Xpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 13, 2021 at 5:51 PM Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2021-04-13 07:12:59 | Re: Retry in pgbench |
| Previous Message | Fujii Masao | 2021-04-13 06:44:40 | Re: TRUNCATE on foreign table |