Bugs in BRIN support - Index corruption and memory leak
|Reported by:||Julien Rouhaud||Owned by:||robe|
I found two bugs in the first BRIN support implementation:
- index corruption bug. It can happen if a geometry is inserted or updated on a previously summarized range (new ranges are not automatically summuraized), and isn't contained in the stored bounding box. This bug is fixed in attached fix_brin_corruption.diff
Please note that this patch expose some required C function which were previously only used for GiST indexes.
- memory leak. The leak is actually in an existing postgis function. I believe it has been unnoticed until now because IFAICT it's only used in GiST indexes, and postgres use a per-tuple MemoryContext for such indexes. This bug is fixed in attached fix_brin_memory_leak.diff
These patches should be applied on 2.3 and trunk.
Change History (11)
comment:7 by , 6 years ago
|Summary:||Bugs in BRIN support → Bugs in BRIN support - Index corruption and memory leak|