CI history

  • #19Dec 08, 2019Grigory Smolkin
  • #17Nov 13, 2019Kyotaro Horiguchi
  • #15Nov 08, 2019Grigory Smolkin
  • #14Nov 08, 2019Grigory Smolkin
  • #9Nov 06, 2019Grigory Smolkin
  • #4Nov 05, 2019Grigory Smolkin
  • #1Nov 04, 2019Grigory Smolkin
  • #19Dec 08, 2019
    recovery_target_latest.sh
    target_latest_PoC_v2.patch
  • #17Nov 13, 2019
    target_latest_PoC.patch
  • #15Nov 08, 2019
    0005-recovery_target_latest.patch
  • #14Nov 08, 2019
    0004-recovery_target_latest.patch
  • #9Nov 06, 2019
    0003-recovery_target_latest.patch
  • #4Nov 05, 2019
    0002-recovery_target_latest.patch
  • #1Nov 04, 2019
    0001-recovery_target_latest.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:t41477
psql -h localhost -U postgres

Built from patchset v19 (message #19), July 28, 2026 at 03:21 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 t41477_19 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 t41477_19 && git checkout t41477_19

Patchset v19 (message #19) is on t41477_19