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: postgrespro/rum
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master@{1day}
Choose a base ref
...
head repository: postgrespro/rum
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: master
Choose a head ref
  • 1 commit
  • 18 files changed
  • 2 contributors

Commits on Dec 23, 2025

  1. [PGPRO-11599] Fix wrong results returned when order_by_attach=TRUE. (#… 

    …164)

With order_by_attach=TRUE, the RUM index arranges the entries in the posting
lists (for keys that have additional information) in order of sorting by
additional information. For the remaining keys, the records are sorted by tid.
The scanGetItemRegular() function assumes that all posting lists have the same
sorting, so it was not suitable for sorting in this case.

In order to fix this, the appropriate TIDs for keys that are ordered by tid are
assembled in advance into a bitmap. For keys ordered in an alternative order, a
routine scan is performed, after which the appropriate tid is checked in the
bitmap.

1. Static functions from TIDBitmap were added to RUM as RumTIDBitmap.
    A function has been added to search for tid inside RumTIDBitmap.
2. Added a test of scanning with keys that are ordered differently.
3. Fixed CI crashes at hardcore level.

---------

Co-authored-by: Arseny Kositsyn <a.kositsyn@postgrespro.ru>
    @arseny114
    2 people authored and Ekaterina Sokolova committed Dec 23, 2025
    Configuration menu
    Copy the full SHA
    292ab36 View commit details
    Browse the repository at this point in the history
Loading