CI history

  • #37Jun 23, 2020Masahiko Sawada
  • #34May 19, 2020Masahiko Sawada
  • #27May 06, 2020Masahiko Sawada
  • #16Apr 24, 2020Peter Geoghegan
  • #13Apr 23, 2020Peter Geoghegan
  • #37Jun 23, 2020
    fix_index_cleanup_v2.patch
  • #34May 19, 2020
    fix_index_cleanup_v2_WIP.patch
  • #27May 06, 2020
    fix_index_cleanup.patch
  • #16Apr 24, 2020
    0003-Mark-lockless-nbtree-leaf-page-memory-undefined.patch
  • #13Apr 23, 2020
    0002-Valgrind-instrumentation.patch

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:t42237
psql -h localhost -U postgres

Built from patchset v37 (message #37), July 28, 2026 at 02:31 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 t42237_37 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 t42237_37 && git checkout t42237_37

Patchset v37 (message #37) is on t42237_37