CI history

  • #37Oct 18, 2018Peter Eisentraut
  • #26Sep 27, 2018Peter Eisentraut
  • #24Sep 01, 2018Peter Eisentraut
  • #16Jun 06, 2018Peter Eisentraut
  • #8Mar 20, 2018Peter Eisentraut
  • #1Feb 21, 2018Peter Eisentraut
  • #37Oct 18, 2018
    v6-0001-pg_upgrade-Allow-use-of-file-cloning.patch
  • #26Sep 27, 2018
    v5-0001-pg_upgrade-Allow-use-of-file-cloning.patch
  • #24Sep 01, 2018
    v4-0001-pg_upgrade-Allow-use-of-file-cloning.patch
  • #16Jun 06, 2018
    v3-0001-pg_upgrade-Allow-use-of-file-cloning.patch
  • #8Mar 20, 2018
    v2-0001-Use-file-cloning-in-pg_upgrade-and-CREATE-DATABAS.patch
  • #1Feb 21, 2018
    0001-Use-file-cloning-in-pg_upgrade-and-CREATE-DATABASE.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:t38229
psql -h localhost -U postgres

Built from patchset v37 (message #37), July 28, 2026 at 05:08 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 t38229_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 t38229_37 && git checkout t38229_37

Patchset v37 (message #37) is on t38229_37