CI history

  • #31Jun 05, 2020Antonin Houska
  • #1Apr 08, 2020Antonin Houska
  • #31Jun 05, 2020
    v02-0001-Check-for-RI-violation-outside-ri_PerformCheck.patch
    v02-0002-Changed-ri_GenerateQual-so-it-generates-the-whole-qu.patch
    + 3 more
  • #1Apr 08, 2020
    v01-0001-Check-for-RI-violation-outside-ri_PerformCheck.patch
    v01-0002-Changed-ri_GenerateQual-so-it-generates-the-whole-qu.patch
    + 2 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:t42198
psql -h localhost -U postgres

Built from patchset v31 (message #31), July 28, 2026 at 02:32 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 t42198_31 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 t42198_31 && git checkout t42198_31

Patchset v31 (message #31) is on t42198_31