From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: ERROR: could not serialize access due to concurrent update
Date: Tue, 16 May 2023 08:44:00 -0500
Message-ID: <0ff97f0c-cc86-8544-0c4d-82900528c69c@gmail.com> (raw)
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>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: ERROR: could not serialize access due to concurrent update
In-Reply-To: <0ff97f0c-cc86-8544-0c4d-82900528c69c@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox