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

Commits on Dec 27, 2025

  1. Use Windows Job Objects to prevent orphaned child processes.

    When the postmaster exits on Windows, backends can continue running
    because Windows lacks Unix's getppid() orphan detection. Orphaned
    backends hold locks and shared memory, preventing clean restart.
    
    Create a Job Object at postmaster startup and assign the postmaster
    to it. Children inherit job membership automatically. Configure with
    KILL_ON_JOB_CLOSE so the kernel terminates all children when the job
    handle closes on postmaster exit.
    
    This is more reliable than existing approaches (inherited handles,
    shared memory flags) because it's kernel-enforced with no polling.
    
    Job creation is allowed to fail non-fatally. Some environments run
    PostgreSQL under an existing job, and Windows 7 disallows nested jobs.
    In such cases we log a message and proceed without orphan protection.
    
    Author: Bryan Green
    dbgreen authored and Commitfest Bot committed Dec 27, 2025
    Configuration menu
    Copy the full SHA
    a92add3 View commit details
    Browse the repository at this point in the history
  2. [CF 6201] v2 - Fix orphaned backend processes on Windows using Job Ob…

    …jects
    
    This branch was automatically generated by a robot using patches from an
    email thread registered at:
    
    https://commitfest.postgresql.org/patch/6201
    
    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/a7109b5f-6590-476c-810c-18f1af588238@gmail.com
    Author(s): Bryan Green
    Commitfest Bot committed Dec 27, 2025
    Configuration menu
    Copy the full SHA
    435c6f0 View commit details
    Browse the repository at this point in the history
Loading