> On 9 Aug 2025, at 18:28, Andrey Borodin <x4...@yandex-team.ru> wrote: > > Also I investigated that in a moment of kill -9 checkpointer flushes heap > page to disk despite content lock. I haven't found who released content lock > though. I've written this message and understood: its LWLockReleaseAll(). 0. checkpointer is going to flush a heap buffer but waits on content lock 1. client is resetting PD_ALL_VISIBLE from page 2. postmaster is killed and command client to go down 3. client calls LWLockReleaseAll() at ProcKill() (?) 4. checkpointer flushes buffer with reset PG_ALL_VISIBLE that is not WAL-logged to standby 5. subsequent deletes do not log resetting this bit 6. deleted data is observable on standby with IndexOnlyScan Any idea how to fix this? Best regards, Andrey Borodin.
- VM corruption on standby Andrey Borodin
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Andrey Borodin
- Re: VM corruption on standby Andrey Borodin
- Re: VM corruption on standby Aleksander Alekseev
- Re: VM corruption on standby Andrey Borodin
- Re: VM corruption on sta... Andrey Borodin
- Re: VM corruption on sta... Aleksander Alekseev
- Re: VM corruption on sta... Kirill Reshke
- Re: VM corruption on sta... Yura Sokolov
- Re: VM corruption on sta... Andrey Borodin
- Re: VM corruption on standby Kirill Reshke
- Re: VM corruption on sta... Yura Sokolov
- Re: VM corruption on sta... Andres Freund
- Re: VM corruption on sta... Yura Sokolov
- Re: VM corruption on standby Kirill Reshke
- Re: VM corruption on standby Kirill Reshke