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

Поиск
Список
Период
Сортировка
От Ron
Тема Re: ERROR: could not serialize access due to concurrent update
Дата
Msg-id 0ff97f0c-cc86-8544-0c4d-82900528c69c@gmail.com
обсуждение исходный текст
Ответ на Re: ERROR: could not serialize access due to concurrent update  (ROHIT SACHDEVA <sachdeva.rohit648@gmail.com>)
Список 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.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 по дате отправления:

Предыдущее
От: ROHIT SACHDEVA
Дата:
Сообщение: Re: ERROR: could not serialize access due to concurrent update
Следующее
От: Uma Annamalai
Дата:
Сообщение: Port 25060 failed: FATAL: pg_hba.conf rejects connection for host on Digital OCean