CI history

  • #13Oct 05, 2017Robert Haas
  • #11Aug 26, 2017Jeff Janes
  • #8Jun 25, 2017Andres Freund
  • #7Jun 20, 2017Jeff Janes
  • #6Jun 15, 2017Jeff Janes
  • #2Jun 14, 2017Jeff Janes
  • #13Oct 05, 2017
    change_walwriter_wakeup_v3.patch
  • #11Aug 26, 2017
    change_walwriter_wakeup_v2.patch
  • #8Jun 25, 2017
    0001-Don-t-signal-latch-owners-if-owner-not-waiting-on-la.patch
  • #7Jun 20, 2017
    pgbench_function.patch
  • #6Jun 15, 2017
    change_walwriter_wakeup.patch
  • #2Jun 14, 2017
    wake_wal_writer_less_aggressively.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:t36921
psql -h localhost -U postgres

Built from patchset v13 (message #13), July 27, 2026 at 10:07 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 t36921_13 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 t36921_13 && git checkout t36921_13

Patchset v13 (message #13) is on t36921_13