Re: [PATCH] Check that index can return in get_actual_variable_range() - Mailing list pgsql-hackers

From Maxime Schoemans
Subject Re: [PATCH] Check that index can return in get_actual_variable_range()
Date
Msg-id 04BA29FF-7FC6-4949-B269-D8D501AF5460@enterprisedb.com
Whole thread Raw
In response to Re: [PATCH] Check that index can return in get_actual_variable_range()  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
> On 28 Oct 2025, at 10:20, Peter Eisentraut <peter@eisentraut.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
assertionsenabled 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
atsome 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.


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Batching in executor
Next
From: Michael Paquier
Date:
Subject: Re: Extend injection_points_attach() to accept a user-defined function