Message-ID: <580a59b7e6ef605000c5dde862300e4290d9445a.camel@cybertec.at>
Subject: Re: ERROR: could not serialize access due to concurrent update
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>,
	pgsql-admin@lists.postgresql.org
Date: Tue, 16 May 2023 17:33:26 +0200
In-Reply-To: 
 <CAKDb7aHL=NXzcFyL5oM3V6=D9P4VVdx_Gd=FskdbeqCotKFSSg@mail.gmail.com>
References: 
	<CAKDb7aFR1B7wvaLBxBDdark7jx=y31BY74WKdrPF1Zq5xwT+mA@mail.gmail.com>
	 <CAKDb7aHL=NXzcFyL5oM3V6=D9P4VVdx_Gd=FskdbeqCotKFSSg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/580a59b7e6ef605000c5dde862300e4290d9445a.camel%40cybertec.at>
Precedence: bulk

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 freq=
uently 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 isolat=
ion?=C2=A0=C2=A0
>
> Also foreign table scan is there on query.

We need more infrmation, like what foreign data wrapper you are using.

Yours,
Laurenz Albe