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: eecd913
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: 9a8d762
Choose a head ref
  • 2 commits
  • 3 files changed
  • 2 contributors

Commits on Oct 17, 2024

  1. Avoid full btree index scans when skipping is possible 

    Previously, we could ignore the skip signal until the end of the range of
values producable by the index scan key. Now, we can fail to start a new
primscan only for up to number of parallel workers + 1 buffers, at the cost
of doing a bit more before releasing the scan while we process the 'we may
need a new primitive scan' signal.

If we detect that a parallel worker in the same primscan range thinks
this is the right moment to start a new primitive scan, we don't release
the parallel scan immediately, but instead only release it after reading
the pages contents to find out if we really should start a new primitive
scan.  If so, we start that new primitive scan, and if instead we find
we've already skidded into the range of pages we would've arrived on with
the skip scan, we instead mark that the primitive scan has reached a new
primscan range, do some cleanup, and then continue the scan as usual.
    @MMeent
    MMeent authored and Commitfest Bot committed Oct 17, 2024
    Configuration menu
    Copy the full SHA
    de5f73f View commit details
    Browse the repository at this point in the history

  2. [CF 50/5299] v1 - Limiting overshoot in nbtree SAOP parallel index scans 

    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/50/5299
Patch(es): https://www.postgresql.org/message-id/CAEze2WibRbQO+wi0cD-QAE6h6WimV=peVbgqT0b8bBDOqGJfrA@mail.gmail.com
Author(s): Matthias van de Meent
    Commitfest Bot committed Oct 17, 2024
    Configuration menu
    Copy the full SHA
    9a8d762 View commit details
    Browse the repository at this point in the history
Loading