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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: ERROR: could not serialize access due to concurrent update
Date: 2023-05-16 15:33:26
Message-ID: 580a59b7e6ef605000c5dde862300e4290d9445a.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Laurenz Albe 2023-05-16 15:34:19 Re: Getting error during execution of pg_dump
Previous Message Wilson Coelho 2023-05-16 15:22:15 Re: Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean