CI history

  • #89Feb 24, 2017Simon Riggs
  • #70Jan 01, 2017Simon Riggs
  • #22Oct 31, 2016Abhijit Menon-Sen
  • #9Sep 06, 2016Abhijit Menon-Sen
  • #2Aug 31, 2016Abhijit Menon-Sen
  • #1Aug 31, 2016Simon Riggs
  • #89Feb 24, 2017
    newRecoveryAPI.v102f.patch
  • #70Jan 01, 2017
    newRecoveryAPI_doc1.v101.patch
    newRecoveryAPI.v101y.patch
  • #22Oct 31, 2016
    recovery_guc_v20161101.patch
  • #9Sep 06, 2016
    recovery_guc_v20160906.patch
  • #2Aug 31, 2016
    recovery_guc_v20160831.patch
  • #1Aug 31, 2016
    recovery_startup_r10_api.v1b.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 retrytests failedCI 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:t35201
psql -h localhost -U postgres

Built from patchset v89 (message #89), July 28, 2026 at 08:18 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 t35201_89 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 t35201_89 && git checkout t35201_89

Patchset v89 (message #89) is on t35201_89