Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: cf/5505~1
Choose a base ref
...
head repository: postgresql-cfbot/postgresql
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: cf/5505
Choose a head ref
  • 4 commits
  • 5 files changed
  • 2 contributors

Commits on Jan 31, 2025

  1. Allow planner support function to return index conditions in OR clause 

    Previously,  as a response to SupportRequestIndexCondition, planner
support functions could return only directly indexable condition but
not multiple index conditions formed in OR clause. To increase the
opportunity to use index in support function uses, this commit enables
get_index_clause_from_support receive OR clauses from support functions,
and use them to build bitmap index scan later
    @yugo-n
    yugo-n authored and Commitfest Bot committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    ddc049a View commit details
    Browse the repository at this point in the history

  2. Allow ILIKE forward matching to use btree index 

    Previously, ILIKE could not use btree index if the pattern
has case-varying characters. To enable it, the planner
support function converts an ILINK operator expression to OR
clause that contains two index clauses for the upper letter and
the lower letter respectively.

For example, "t ILIKE '123foo%'" can be converted to
"(t <= '123F'AND t > '123G') OR (t <= '123f' AND t < '123g')",
and bitmap index scan plan could be used for this.
    @yugo-n
    yugo-n authored and Commitfest Bot committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    dccb1f2 View commit details
    Browse the repository at this point in the history

  3. Allow ILIKE forward matching to use spgist index 

    Previously, ILIKE could not use spgist index if the pattern
has case-varying characters. To enable it, the planner
support function converts an ILINK operator expression to OR
clause that contains two index clauses for the upper letter and
the lower letter respectively.
    @yugo-n
    yugo-n authored and Commitfest Bot committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    fb332fb View commit details
    Browse the repository at this point in the history

  4. [CF 52/5505] v2 - Allow to use an index for ILIKE in more cases 

    This commit was automatically generated by a robot at cfbot.cputube.org.
It is based on patches submitted to the PostgreSQL mailing lists and
registered in the PostgreSQL Commitfest application.

This branch will be overwritten each time a new patch version is posted to
the email thread, and also periodically to check for bitrot caused by changes
on the master branch.

Commitfest entry: https://commitfest.postgresql.org/52/5505
Patch(es): https://www.postgresql.org/message-id/[email protected]
Author(s): Yugo Nagata
    Commitfest Bot committed Jan 31, 2025
    Configuration menu
    Copy the full SHA
    a8188b7 View commit details
    Browse the repository at this point in the history
Loading