Postgres Pro
Downloads
Home   >   mailing lists

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

From Ron
Subject Re: ERROR: could not serialize access due to concurrent update
Date
Msg-id 0ff97f0c-cc86-8544-0c4d-82900528c69c@gmail.com
Whole thread Raw
In response to Re: ERROR: could not serialize access due to concurrent update  (ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>)
List pgsql-admin
Tree view
Scan, you say?  Add an index to support the FK lookup.

On 5/16/23 08:09, ROHIT SACHDEVA wrote:
Also foreign table scan is there on query.

On Tue, May 16, 2023 at 6:08 PM ROHIT SACHDEVA <sachdeva.rohit648@gmail.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

--
Born in Arizona, moved to Babylonia.

pgsql-admin by date:

Previous
From: ROHIT SACHDEVA
Date:
Subject: Re: ERROR: could not serialize access due to concurrent update
Next
From: Uma Annamalai
Date:
Subject: Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean