Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c)
От
Andres Freund
Тема
Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c)
Дата
Msg-id
20220213214317.qhroocro46ligj6w@alap3.anarazel.de
Ответ на
[PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) (Ranier Vilela)
Список
Дерево обсуждения
[PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) Ranier Vilela <ranier.vf@gmail.com>
Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) Andres Freund <andres@anarazel.de>
Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) Tomas Vondra <tomas.vondra@enterprisedb.com>
Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) Tom Lane <tgl@sss.pgh.pa.us>
Re: [PATCH] Avoid open and lock the table Extendend Statistics (src/backend/commands/statscmds.c) Ranier Vilela <ranier.vf@gmail.com>
Hi, On 2022-02-13 18:21:38 -0300, Ranier Vilela wrote: > Why open and lock the table Extended Statistics if it is not the owner. > Check and return to avoid this. I was about to say that this opens up time-to-check-time-to-use type issues. But it's the wrong thing to lock to prevent those. Having looked briefly at it, I don't understand what the locking scheme is? Shouldn't there be at least some locking against concurrent ALTERs and between ALTER and ANALYZE etc? Greetings, Andres Freund
В списке pgsql-hackers по дате отправления
