pgsql: Fix reuse-after-free hazard in dead_items_reset

2025-10-03 Thread John Naylor
Fix reuse-after-free hazard in dead_items_reset In similar vein to commit ccc8194e427, a reset instance of a shared memory TID store happened to occupy the same private memory as the old one for the entry point, since the chunk freed after the last round of index vacuuming was put on the context's

pgsql: Fix reuse-after-free hazard in dead_items_reset

2025-10-03 Thread John Naylor
Fix reuse-after-free hazard in dead_items_reset In similar vein to commit ccc8194e427, a reset instance of a shared memory TID store happened to occupy the same private memory as the old one for the entry point, since the chunk freed after the last round of index vacuuming was put on the context's

pgsql: Fix reuse-after-free hazard in dead_items_reset

2025-10-03 Thread John Naylor
Fix reuse-after-free hazard in dead_items_reset In similar vein to commit ccc8194e427, a reset instance of a shared memory TID store happened to occupy the same private memory as the old one for the entry point, since the chunk freed after the last round of index vacuuming was put on the context's