| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: could not serialize access due to concurrent update |
| Date: | 2023-05-16 18:08:45 |
| Message-ID: | 474BDC88-BFEA-4D62-9D43-E0E7ABA1A13A@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On May 16, 2023, at 11:24 AM, ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com> wrote:
>
> But due to this error our transaction is aborted and application team are getting these errors in their logs.
>
> How can I figure this out?
> Can there be work around for not getting this error.
As suggested previously, repeat the query.
It would be good, of course, to reduce the frequency of the errors by figuring out what is conflicting--are the queries generally taking too long compared to their frequency? But repeating a query when a lock conflict blocks it would still be the ultimate fallback, and is pretty standard practice.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wolfgang Wilhelm | 2023-05-16 19:32:33 | Re: Options for more aggressive space reclamation in vacuuming? |
| Previous Message | ROHIT SACHDEVA | 2023-05-16 17:24:20 | Re: ERROR: could not serialize access due to concurrent update |