CI history

  • #14Dec 30, 2020David Fetter
  • #10Apr 08, 2020David Fetter
  • #8Jan 17, 2020David Fetter
  • #3Dec 12, 2019David Fetter
  • #1Dec 12, 2019David Fetter
  • #14Dec 30, 2020
    v5-0001-Enable-setting-pg_hba.conf-permissions-from-initd.patch
  • #10Apr 08, 2020
    v4-0001-Enable-setting-pg_hba.conf-permissions-from-initd.patch
  • #8Jan 17, 2020
    v3-0001-Enable-setting-pg_hba.conf-permissions-from-initd.patch
  • #3Dec 12, 2019
    v2-0001-Enable-setting-pg_hba.conf-permissions-from-initd.patch
  • #1Dec 12, 2019
    v1-0001-Enable-setting-pg_hba.conf-permissions-from-initd.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:t41655
psql -h localhost -U postgres

Built from patchset v14 (message #14), July 27, 2026 at 05:56 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 t41655_14 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 t41655_14 && git checkout t41655_14

Patchset v14 (message #14) is on t41655_14