> On 7 Aug 2025, at 17:09, Aleksander Alekseev <aleksan...@tigerdata.com> wrote:
> 
> If my understanding is correct, we should make a WAL record with the
> XLH_LOCK_ALL_FROZEN_CLEARED flag *before* we modify the VM but within
> the same critical section (in order to avoid race conditions within
> the same backend).

Well, the test passes because you moved injection point to a very safe 
position. I can't comment anything on other aspects of moving 
visibilitymap_clear() around.
The approach seems viable to me, but I'd like to have understanding why 
PD_ALL_VISIBLE in a heap page header did not save the day before fixing 
anything.


Best regards, Andrey Borodin.

Reply via email to