CI history

  • #11Oct 09, 2025Aleksander Alekseev
  • #9Oct 09, 2025Aleksander Alekseev
  • #8Oct 09, 2025Aleksander Alekseev
  • #2Oct 08, 2025Aleksander Alekseev
  • #1Oct 08, 2025Aleksander Alekseev
  • #11Oct 09, 2025
    v5-0001-Remove-unused-include-s.patch
  • #9Oct 09, 2025
    v4-0001-Remove-unused-include-s.patch
  • #8Oct 09, 2025
    v3-0001-Remove-unused-include-s.patch
  • #2Oct 08, 2025
    v2-0001-Remove-unused-include-s-in-src-backend-commands.patch
  • #1Oct 08, 2025
    v1-0001-Remove-unused-include-s-in-src-backend-commands.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:t52412
psql -h localhost -U postgres

Built from patchset v11 (message #11), July 27, 2026 at 07:12 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 t52412_11 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 t52412_11 && git checkout t52412_11

Patchset v11 (message #11) is on t52412_11