From: | ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: ERROR: could not serialize access due to concurrent update |
Date: | 2023-05-16 17:24:20 |
Message-ID: | CAKDb7aFLkz2btDpnkmefDBa-N=kUJ9HYhPmmD1o5+sLqYewY6A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Okay ..
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.
On Tue, 16 May, 2023, 10:05 pm Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at>
wrote:
> >
> On Tue, 2023-05-16 at 18:39 +0530, ROHIT SACHDEVA wrote:
> > I am getting this error in the application logs, and this error is
> frequently coming.
> > Could someone suggest what would be the best solution to overcome these
> types of errors.
> > Isolation of the database is read committed. Should I change the
> isolation?
> >
> > Also foreign table scan is there on query.
> >
> > It's a postgres_fdw i am using.
>
> That is normal if you modify any data via FDW, because one local query can
> result in several
> foreign queries, which have to see the same snapshot of the data.
>
> Repeat queries that fail that way, and keep your transactions as short as
> you can.
>
> Yours,
> Laurenz Albe
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2023-05-16 18:08:45 | Re: ERROR: could not serialize access due to concurrent update |
Previous Message | Laurenz Albe | 2023-05-16 16:35:00 | Re: ERROR: could not serialize access due to concurrent update |