pgsql: Restore lock level to update statusFlags
От | Alvaro Herrera |
---|---|
Тема | pgsql: Restore lock level to update statusFlags |
Дата | |
Msg-id | E1kiJLn-00034P-7b@gemulon.postgresql.org обсуждение исходный текст |
Список | pgsql-committers |
Restore lock level to update statusFlags Reverts 27838981be9d (some comments are kept). Per discussion, it does not seem safe to relax the lock level used for this; in order for it to be safe, there would have to be memory barriers between the point we set the flag and the point we set the trasaction Xid, which perhaps would not be so bad; but there would also have to be barriers at the readers' side, which from a performance perspective might be bad. Now maybe this analysis is wrong and it *is* safe for some reason, but proof of that is not trivial. Discussion: https://postgr.es/m/20201118190928.vnztes7c2sldu43a@alap3.anarazel.de Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/dcfff74fb16622898a9d1df33e530f477caab095 Modified Files -------------- src/backend/commands/vacuum.c | 20 +++++++++++--------- src/backend/replication/logical/logical.c | 2 +- src/backend/storage/ipc/procarray.c | 8 +++----- src/include/storage/proc.h | 6 +++--- 4 files changed, 18 insertions(+), 18 deletions(-)
В списке pgsql-committers по дате отправления: