| From: | Ron <ronljohnsonjr(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:44:00 |
| Message-ID: | 0ff97f0c-cc86-8544-0c4d-82900528c69c@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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(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
--
Born in Arizona, moved to Babylonia.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Uma Annamalai | 2023-05-16 13:48:05 | Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean |
| Previous Message | ROHIT SACHDEVA | 2023-05-16 13:09:16 | Re: ERROR: could not serialize access due to concurrent update |