Re: ERROR: could not serialize access due to concurrent update - Mailing list pgsql-admin

From ROHIT SACHDEVA
Subject Re: ERROR: could not serialize access due to concurrent update
Date
Msg-id CAKDb7aGaZ94nxr1gSw2NfLu5arec9G+SOBDGRV7njxG_C5TZeg@mail.gmail.com
Whole thread Raw
In response to Re: ERROR: could not serialize access due to concurrent update  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: ERROR: could not serialize access due to concurrent update
List pgsql-admin
It's a postgres_fdw i am using.


On Tue, 16 May, 2023, 9:03 pm Laurenz Albe, <laurenz.albe@cybertec.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

pgsql-admin by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Getting error during execution of pg_dump
Next
From: Laurenz Albe
Date:
Subject: Re: ERROR: could not serialize access due to concurrent update