From: | Tender Wang <tndrwang(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: A little cosmetic to convert_VALUES_to_ANY() |
Date: | 2025-08-01 14:45:20 |
Message-ID: | CAHewXNkAcF0N-Kims+-zd0Y2Mr8UES5vwHjqRUOEtR5G4tnZGw@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tender Wang <tndrwang(at)gmail(dot)com> 于2025年7月27日周日 15:53写道:
> Hi,
>
> While debugging the pull-up sublink codes, I noticed the
> convert_VALUES_to_ANY().
> The function is to convert "where colX in VALUES(xxx)" into SAOP. It
> firstly scans the values_list to
> make sure no volatile function is in this list, then it scans this
> values_list again to check that it
> only includes Const items.
>
> We can merge the two scans into one. This can reduce the time complexity
> from 2O(n) to O(n).
>
> Also, add a brace for better/more consistent style in the attached patch.
>
>
I have added this to the commitfest in [1]. I hope someone can help me
review it.
[1] https://commitfest.postgresql.org/patch/5937/
--
Thanks,
Tender Wang
From | Date | Subject | |
---|---|---|---|
Next Message | Alexandra Wang | 2025-08-01 14:58:01 | Re: Pathify RHS unique-ification for semijoin planning |
Previous Message | Andrei Lepikhov | 2025-08-01 14:33:17 | Re: SQL function to access to `creating_extension` |