Re: VM corruption on standby
От | Yura Sokolov |
---|---|
Тема | Re: VM corruption on standby |
Дата | |
Msg-id | 91495849-ebf7-4f7e-8cca-ec718964d256@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: VM corruption on standby (Kirill Reshke <reshkekirill@gmail.com>) |
Ответы |
Re: VM corruption on standby
|
Список | pgsql-hackers |
09.08.2025 22:54, Kirill Reshke пишет: > On Thu, 7 Aug 2025 at 21:36, Aleksander Alekseev > <aleksander@tigerdata.com> wrote: > >> Perhaps there was a good >> reason to update the VM *before* creating WAL records I'm unaware of. > > Looks like 503c730 intentionally does it this way; however, I have not > yet fully understood the reasoning behind it. I repeat: there was no intention. Neither in commit message, nor in discussion about. There was intention to move visibilitymap_clear under heap page lock and into critical section, but there were no any word about logging. I believe, it was just an unfortunate oversight that the change is made before logging. -- regards Yura Sokolov aka funny-falcon
В списке pgsql-hackers по дате отправления: