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

From: ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: ERROR: could not serialize access due to concurrent update
Date: 2023-05-16 13:09:16
Message-ID: CAKDb7aHL=NXzcFyL5oM3V6=D9P4VVdx_Gd=FskdbeqCotKFSSg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Also foreign table scan is there on query.

On Tue, May 16, 2023 at 6:08 PM ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com>
wrote:

> Hi All,
> 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?
>
>
> --
> Have a Good day !!!
>
> Regards
> Rohit Sachdeva
>

--
Have a Good day !!!

Regards
Rohit Sachdeva

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ron 2023-05-16 13:44:00 Re: ERROR: could not serialize access due to concurrent update
Previous Message ROHIT SACHDEVA 2023-05-16 12:38:04 ERROR: could not serialize access due to concurrent update