Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor the IN operator to use '= ANY()' syntax (#1236) #1488

Merged
merged 1 commit into from
Jan 4, 2024

Conversation

jrgemignani
Copy link
Contributor

This change reduces use of internal function calls from the IN implementation to optimize performance. This also changes IN behavior to correctly return NULL upon NULL elements included in the list that IN checks against.

Added and corrected regression tests.

Corrected for lack of A_Const field isnull and needed #include files.

Corrected for lack of function availability in PG12

Co-authored by: Dehowe Feng [email protected]
Co-authored by: Josh Innis [email protected]

This change reduces use of internal function calls from the
IN implementation to optimize performance. This also changes
IN behavior to correctly return NULL upon NULL elements
included in the list that IN checks against.

Added and corrected regression tests.

Corrected for lack of A_Const field isnull and needed #include
files.

Corrected for lack of function availability in PG12

Co-authored by: Josh Innis <[email protected]>
@github-actions github-actions bot added the PG11 PostgreSQL11 label Jan 4, 2024
@rafsun42 rafsun42 merged commit a1cc1c9 into apache:PG11 Jan 4, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PG11 PostgreSQL11
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants