CI history

  • #19Aug 29, 2020Dilip Kumar
  • #13Jul 21, 2020Dilip Kumar
  • #12Jul 21, 2020Dilip Kumar
  • #1Jul 17, 2020Dilip Kumar
  • #19Aug 29, 2020
    v4-0001-Provide-a-GUC-to-allow-vacuum-to-continue-on-corr.patch
  • #13Jul 21, 2020
    v3-0001-Provide-a-GUC-to-allow-vacuum-to-continue-on-corr.patch
  • #12Jul 21, 2020
    v2-0001-Provide-a-GUC-to-allow-vacuum-to-continue-on-corr.patch
  • #1Jul 17, 2020
    v1-0001-Provide-a-GUC-to-allow-vacuum-to-continue-on-corr.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:t42694
psql -h localhost -U postgres

Built from patchset v19 (message #19), July 27, 2026 at 06:47 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 t42694_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 t42694_19 && git checkout t42694_19

Patchset v19 (message #19) is on t42694_19