Re: [PATCH] Check that index can return in get_actual_variable_range()

From: Maxime Schoemans <maxime(dot)schoemans(at)enterprisedb(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Aleksander Alekseev <aleksander(at)tigerdata(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com>
Subject: Re: [PATCH] Check that index can return in get_actual_variable_range()
Date: 2025-10-28 13:28:30
Message-ID: 04BA29FF-7FC6-4949-B269-D8D501AF5460@enterprisedb.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> On 28 Oct 2025, at 10:20, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> I have committed the first patch.

Great, thank you for looking at this.

> The test suite is probably a bit too bulky for testing this particular niche behavior. Also, it doesn't work with assertions enabled because of the hardcoded BTREE_AM_OID in src/include/access/nbtree.h. So I don't plan to commit that. But it's good to have it in the archive, and perhaps it can be part of a larger test suite for the index AM API at some point in the future.

And I agree, the test suite is probably overkill for this two-line patch, but it might be good to have around for later.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2025-10-28 13:33:09 Re: Extend injection_points_attach() to accept a user-defined function
Previous Message Amit Langote 2025-10-28 13:11:46 Re: Batching in executor