CI history

  • #11Dec 19, 2022Shinoda, Noriyoshi (PN Japan FSIP)fix on top of #6LLM analysis, 95% sure
  • #6Dec 14, 2022Peter Eisentrautsmall revision of #1LLM analysis, 100% sure
  • #1Dec 01, 2022Peter Eisentrautnew seriesLLM analysis, 100% sure
  • #11Dec 19, 2022
    pg_upgrade_check_mode_v1.diff
  • #6Dec 14, 2022
    v2-0001-pg_upgrade-Add-copy-option.patch
    v2-0002-pg_upgrade-Make-testing-different-transfer-modes-.patch
  • #1Dec 01, 2022
    0001-pg_upgrade-Add-copy-option.patch
    0002-pg_upgrade-Make-testing-different-transfer-modes-eas.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:t47032
psql -h localhost -U postgres

Built from patchset v11 (message #11), August 18, 2026 at 03:39 PM.

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 t47032_11 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 t47032_11 && git checkout t47032_11

Patchset v11 (message #11) is on t47032_11