| From: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
|---|---|
| To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
| Cc: | Maxime Schoemans <maxime(dot)schoemans(at)enterprisedb(dot)com>, pgsql-hackers mailing list <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Multi-Entry Indexing for GiST & SP-GiST |
| Date: | 2026-06-02 08:14:45 |
| Message-ID: | 80D43BB9-DB73-4442-9268-8DAC3254B052@yandex-team.ru |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 1 Jun 2026, at 20:35, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jelte Fennema-Nio | 2026-06-02 08:31:36 | Re: PostgreSQL 19 Beta 1 release announcement draft |
| Previous Message | Peter Smith | 2026-06-02 08:10:35 | Re: Proposal: Conflict log history table for Logical Replication |