CI history

  • #5Jul 09, 23:09Tomas Vondra
  • #4Jul 08, 00:31Andreas Karlsson
  • #1May 04, 08:18Tomas Vondra
  • #5Jul 09, 23:09
    v3-0003-Toy-extension-to-make-it-easier-to-test-out-of-bo.patch
    v3-0002-valgrind-Add-NOACCESS-sentinels-to-allocations-in.patch
    + 1 more
  • #4Jul 08, 00:31
    v2-0001-valgrind-Add-NOACCESS-sentinels-for-shm_toc-entri.patch
    v2-0002-valgrind-Add-NOACCESS-sentinels-to-allocations-in.patch
    + 1 more
  • #1May 04, 08:18
    0001-valgrind-add-NOACCESS-sentinels-for-dynamic-shmem.patch
    valgrind.log

Beta feature Hackorum builds and tests every patch posted to the lists, not only commitfest submissions. This is Hackorum's own CI rather than the PostgreSQL project's, and it is still under testing - please report anything that looks wrong.

won't retrysuccessCI history

You can run a PostgreSQL built from this patch straight from Docker, with no checkout and no build:

docker run --rm -p 5432:5432 ghcr.io/hackorum-dev/postgres-patch:t139546
psql -h localhost -U postgres

Built from patchset v5 (message #5), September 18, 2026 at 06:36 AM.

Every patchset is also pushed to a branch of our PostgreSQL fork, so you can check out the same tree CI built. Without a PostgreSQL checkout:

git clone --branch t139546_5 https://github.com/hackorum-dev/postgres.git

In a checkout you already have, add the fork once:

git remote add hackorum https://github.com/hackorum-dev/postgres.git

then, for this patchset and every later one:

git fetch hackorum t139546_5 && git checkout t139546_5

Patchset v5 (message #5) is on t139546_5