Re: Adding skip scan (including MDAM style range skip scan) to nbtree

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tomas Vondra <tomas(at)vondra(dot)me>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Adding skip scan (including MDAM style range skip scan) to nbtree
Date: 2025-05-12 12:58:15
Message-ID: CAH2-WznJVh46LPDmkOo95zyanBdMteX5gDQpo6roZeYP4kq+bQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, May 11, 2025 at 11:09 PM Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> I where "revert" is master with the removal patch. Sorry about the
> confusion, I guess I was distracted and did some mistake.
>
> So, this seems to be in line with the hypothesis ...

That makes way more sense.

I wonder if we can fix this problem by getting rid of the old support
routine #5, "options". It currently doesn't do anything, and I always
thought it was strange that it was added "for uniformity" with other
index AMs.

OTOH, one could argue that it's only a matter of time until somebody
needs to add another support routine to nbtree; why delay dealing with
the problem that you've highlighted? Right now I don't really have an
opinion on how best to address the problem.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Álvaro Herrera 2025-05-12 14:13:37 Re: Why our Valgrind reports suck
Previous Message Amit Kapila 2025-05-12 12:30:03 Re: Vacuum statistics