| From: | Ilya Kosmodemiansky <ik(at)dataegret(dot)com> |
|---|---|
| To: | "Wirch, Eduard" <eduard(dot)w(at)smart-host(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: PostgreSql: Canceled on conflict out to old pivot |
| Date: | 2023-11-28 06:14:38 |
| Message-ID: | EA2D97DA-68E7-44E4-BDD3-061826B6C583@dataegret.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
> On 28. Nov 2023, at 06:41, Wirch, Eduard <eduard(dot)w(at)smart-host(dot)com> wrote:
>
>
>
> :
>
> ERROR: could not serialize access due to read/write dependencies among transactions
> Detail: Reason code: Canceled on identification as a pivot, with conflict out to old committed transaction 61866959.
>
> There is a variation of the error:
>
> PSQLException: ERROR: could not serialize access due to read/write dependencies among transactions
> Detail: Reason code: Canceled on conflict out to old pivot 61940806.
Could you show explain analyze output for those queries which fail with such errors?
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2023-11-28 06:28:27 | Re: BackgroundPsql's set_query_timer_restart() may not work |
| Previous Message | Wirch, Eduard | 2023-11-28 05:41:31 | PostgreSql: Canceled on conflict out to old pivot |