Re: Spurious pgstat_drop_replslot() call
От
Michael Paquier
Тема
Re: Spurious pgstat_drop_replslot() call
Дата
Msg-id
ZfDZIgkzQnkPpGsC@paquier.xyz
Ответ на
Re: Spurious pgstat_drop_replslot() call (Alexander Lakhin)
Список
Дерево обсуждения
Spurious pgstat_drop_replslot() call Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Re: Spurious pgstat_drop_replslot() call Michael Paquier <michael@paquier.xyz>
Re: Spurious pgstat_drop_replslot() call Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Re: Spurious pgstat_drop_replslot() call Michael Paquier <michael@paquier.xyz>
Re: Spurious pgstat_drop_replslot() call Michael Paquier <michael@paquier.xyz>
Re: Spurious pgstat_drop_replslot() call Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
Re: Spurious pgstat_drop_replslot() call Alexander Lakhin <exclusion@gmail.com>
Re: Spurious pgstat_drop_replslot() call Michael Paquier <michael@paquier.xyz>
Re: Spurious pgstat_drop_replslot() call Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
On Tue, Mar 12, 2024 at 12:00:00PM +0300, Alexander Lakhin wrote: > Sorry for a bit off-topic, but I've remembered an anomaly with a similar > assert: > https://www.postgresql.org/message-id/17947-b9554521ad963c9c%40postgresql.org Thanks for the reminder. The invalidation path with the stats drop is only in 16~. > Maybe you would find it worth considering while working in this area... > (I've just run that reproducer on b36fbd9f8 and confirmed that the > assertion failure is still here.) Indeed, something needs to happen. I am not surprised that it still reproduces; nothing has changed with the locking of the stats entries. :/ -- Michael
В списке pgsql-hackers по дате отправления
От: Jelte Fennema-Nio
Дата: