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/5703~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/5703
Choose a head ref
  • 2 commits
  • 11 files changed
  • 2 contributors

Commits on Jul 5, 2025

  1. Add capability to interleave shared memory across multiple NUMA nodes.

    Introduce new GUC numa=off(default)/auto/all/../=../@.. that might be used to
    enable interleaving of shared memory. Until today, imbalances in shared memory
    allocations on NUMA setups, may have caused non-deterministic performance
    due to differences in latencies and bandwidths across interconnects ("remote"
    access).
    
    When provided list of nodes, the default is to use interleave memory on
    preferred NUMA nodes, but support for more strict modes: pinning memory or
    pinning both memory and CPU to specific NUMA node(s) is handled using special
    '=' and '@' prefixes.
    
    This is only supported on Linux with libnuma.
    
    Author: Jakub Wartak <jakub.wartak@enterprisedb.com>
    Inspired-by: Andres Freund <andres@anarazel.de>
    Reviewed-by:
    Discussion: https://postgr.es/m/CAKZiRmw6i1W1AwXxa-Asrn8wrVcVH3TO715g_MCoowTS9rkGyw%40mail.gmail.com
    jakubwartakEDB authored and Commitfest Bot committed Jul 5, 2025
    Configuration menu
    Copy the full SHA
    cc43553 View commit details
    Browse the repository at this point in the history
  2. [CF 5703] v4 - NUMA shared memory interleaving

    This branch was automatically generated by a robot using patches from an
    email thread registered at:
    
    https://commitfest.postgresql.org/patch/5703
    
    The branch will be overwritten each time a new patch version is posted to
    the thread, and also periodically to check for bitrot caused by changes
    on the master branch.
    
    Patch(es): https://www.postgresql.org/message-id/CAKZiRmy4r+CYFX+x7fAj9t4tjMJZnBY73phuBVM7pbEfxueiEg@mail.gmail.com
    Author(s): Jakub Wartak
    Commitfest Bot committed Jul 5, 2025
    Configuration menu
    Copy the full SHA
    90a0393 View commit details
    Browse the repository at this point in the history
Loading