CI history

  • #5Sep 20, 2017Peter Eisentraut
  • #3Aug 22, 2017Peter Eisentraut
  • #1Aug 11, 2017Peter Eisentraut
  • #5Sep 20, 2017
    v3-0007-Improve-vpath-support-in-plperl-build.patch
    v3-0008-Support-coverage-on-vpath-builds.patch
    + 7 more
  • #3Aug 22, 2017
    v2-0001-Run-only-top-level-recursive-lcov.patch
    v2-0002-Have-lcov-exclude-external-files.patch
    + 7 more
  • #1Aug 11, 2017
    0002-Have-lcov-exclude-external-files.patch
    0001-Run-only-top-level-recursive-lcov.patch
    + 7 more

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:t37250
psql -h localhost -U postgres

Built from patchset v5 (message #5), July 27, 2026 at 10:15 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 t37250_5 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 t37250_5 && git checkout t37250_5

Patchset v5 (message #5) is on t37250_5