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

From Laurenz Albe
Subject Re: ERROR: could not serialize access due to concurrent update
Date
Msg-id 580a59b7e6ef605000c5dde862300e4290d9445a.camel@cybertec.at
Whole thread Raw
In response to Re: ERROR: could not serialize access due to concurrent update  (ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>)
Responses Re: ERROR: could not serialize access due to concurrent update
List pgsql-admin
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: Wilson Coelho
Date:
Subject: Re: Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean
Next
From: Laurenz Albe
Date:
Subject: Re: Getting error during execution of pg_dump