Re: BTScanOpaqueData size slows down tests

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: BTScanOpaqueData size slows down tests
Date: 2025-04-02 16:12:35
Message-ID: CAH2-WznHQbQJ7rfXHv_d2K3K+r4qrZxPxn64AK4cGu1oZzQQxQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 2, 2025 at 12:10 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I could get behind the idea of just having enough space in
> BTScanOpaqueData for about ten items, and dynamically allocating
> a MaxTIDsPerBTreePage-sized array only if we overrun that.
> And not allocate any space for mark/restore unless a mark is
> done.

That's exactly what I had in mind.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2025-04-02 16:20:57 Re: Incorrect result of bitmap heap scan.
Previous Message Tom Lane 2025-04-02 16:10:43 Re: BTScanOpaqueData size slows down tests