Re: Saving stack space in nbtree's _bt_first function - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Saving stack space in nbtree's _bt_first function
Date
Msg-id CAH2-WzkH=07vK8zEeJEf0xbyV77QgTJ9A6AHD52sPbnHH1cs8Q@mail.gmail.com
Whole thread Raw
In response to Re: Saving stack space in nbtree's _bt_first function  (Mircea Cadariu <cadariu.mircea@gmail.com>)
List pgsql-hackers
On Wed, Jul 16, 2025 at 9:17 AM Mircea Cadariu <cadariu.mircea@gmail.com> wrote:
> Thanks for the elaboration and updated patch! Indeed, I see it's set in
> the ScanKeyEntryInitialize to either BTGreaterStrategyNumber or
> BTLessStrategyNumber, then few lines lower there's the if with the break.
>
> I'm convinced.

Pushed.

> I noticed this CI job failure for the V2, seems unrelated to the subject
> of the patch though, does it need a retry?
> https://cirrus-ci.com/task/5781246762024960

It must be unrelated. I didn't see any such failure myself just now,
and I can't imagine how it could possibly be relevant.

Thanks for the review
--
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: pg_dumpall dumps global objects with --statistics-only or --no-schema
Next
From: Nathan Bossart
Date:
Subject: Re: small fix for pg_overexplain docs