Re: ERROR: could not serialize access due to concurrent update

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 16:21:53
Message-ID: CAKDb7aGaZ94nxr1gSw2NfLu5arec9G+SOBDGRV7njxG_C5TZeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

It's a postgres_fdw i am using.

On Tue, 16 May, 2023, 9:03 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.
>
> We need more infrmation, like what foreign data wrapper you are using.
>
> Yours,
> Laurenz Albe
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2023-05-16 16:35:00 Re: ERROR: could not serialize access due to concurrent update
Previous Message Laurenz Albe 2023-05-16 15:34:19 Re: Getting error during execution of pg_dump