Re: Improve join_search_one_level readibilty (one line change) - Mailing list pgsql-hackers

From David Rowley
Subject Re: Improve join_search_one_level readibilty (one line change)
Date
Msg-id CAApHDvrvO724r32LRW-GS6UVqFNO7FXDHcNM3UZd+4hagKZBxQ@mail.gmail.com
Whole thread Raw
In response to Re: Improve join_search_one_level readibilty (one line change)  (Richard Guo <guofenglinux@gmail.com>)
List pgsql-hackers
On Fri, 4 Aug 2023 at 16:05, Richard Guo <guofenglinux@gmail.com> wrote:
>
>
> On Fri, Aug 4, 2023 at 10:36 AM David Rowley <dgrowleyml@gmail.com> wrote:
>>
>> The whole lnext() stuff all feels a bit old now that Lists are arrays.
>> I think we'd be better adjusting the code to pass the List index where
>> we start from rather than the ListCell to start from.  That way we can
>> use for_each_from() to iterate rather than for_each_cell().  What's
>> there today feels a bit crufty and there's some element of danger that
>> the given ListCell does not even belong to the given List.
>
>
> I think we can go even further to do the same for 'bushy plans' case,
> like the attached.

Seems like a good idea to me. I've pushed that patch.

Alex, many thanks for highlighting this and posting a patch to fix it.
Congratulations on your first patch being committed.

David



pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: How to add a new operator for parser?
Next
From: Masahiko Sawada
Date:
Subject: Re: [PoC] pg_upgrade: allow to upgrade publisher node