Re: Is this expected concurrency behaviour for EvalPlanQual and ctid?

Поиск
Список
Период
Сортировка
От Sophie Alpert
Тема Re: Is this expected concurrency behaviour for EvalPlanQual and ctid?
Дата
Msg-id 702bca7b-711f-4d7c-ad39-dead6a628374@app.fastmail.com
обсуждение
Ответ на Re: Is this expected concurrency behaviour for EvalPlanQual and ctid?  (Bernice Southey <bernice.southey@gmail.com>)
Список pgsql-general
Bernice,

Perhaps you'll find this explanation I wrote around interactions between EvalPlanQual and ctid filters helpful:
https://stackoverflow.com/a/79757326/49485

The short answer is that even after my fix, you likely don't want to filter an UPDATE or DELETE on ctid values that
werefirst retrieved in the same SQL statement, because the ctid can have changed in between the time of the initial
readand the time of locking (and thus the recheck will fail).
 

Sophie



В списке pgsql-general по дате отправления: