| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | ROHIT SACHDEVA <sachdeva(dot)rohit648(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: could not serialize access due to concurrent update |
| Date: | 2023-05-16 16:35:00 |
| Message-ID: | 6d2162718b0af8504c5f85013b78dc97a2046d59.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.
>
> It's a postgres_fdw i am using.
That is normal if you modify any data via FDW, because one local query can result in several
foreign queries, which have to see the same snapshot of the data.
Repeat queries that fail that way, and keep your transactions as short as you can.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ROHIT SACHDEVA | 2023-05-16 17:24:20 | Re: ERROR: could not serialize access due to concurrent update |
| Previous Message | ROHIT SACHDEVA | 2023-05-16 16:21:53 | Re: ERROR: could not serialize access due to concurrent update |