pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau

pgsql: Remove unnecessary complication around xmlParseBalancedChunkMemo

2025-07-29 Thread Tom Lane
Remove unnecessary complication around xmlParseBalancedChunkMemory. When I prepared 71c0921b6 et al yesterday, I was thinking that the logic involving explicitly freeing the node_list output was still needed to dodge leakage bugs in libxml2. But I was misremembering: we introduced that only becau