> On 1 Jun 2026, at 20:35, Matthias van de Meent <[email protected]> > wrote: > > Could you help me understand how this deduplication works? Wouldn't > this possibly use ~ unbounded memory (or however much memory is needed > to store up to 2^48 TIDs)? For practical IndexScan this should not matter much. For impractical we can guarantee result by unique tuplestore when hashtable\ART is over WORK_MEM. Best regards, Andrey Borodin.
- Multi-Entry Indexing for GiST & SP-GiST Maxime Schoemans
- Re: Multi-Entry Indexing for GiST & SP-GiST Andrey Borodin
- Re: Multi-Entry Indexing for GiST & SP-GiST Matthias van de Meent
- Re: Multi-Entry Indexing for GiST & SP-... Andrey Borodin
