CI history

  • #14Mar 06, 2020Dent John
  • #13Feb 22, 2020Dent John
  • #11Jan 25, 2020Dent John
  • #10Jan 19, 2020Dent John
  • #3Dec 14, 2019Dent John
  • #1Sep 17, 2019Dent John
  • #14Mar 06, 2020
    unnest-refcursor-v7a.patch
  • #13Feb 22, 2020
    unnest-refcursor-v6a.patch
  • #11Jan 25, 2020
    unnest-refcursor-v5a.patch
  • #10Jan 19, 2020
    unnest-refcursor-v4.patch
  • #3Dec 14, 2019
    unnest-refcursor-v3.patch
  • #1Sep 17, 2019
    unnest-refcursor-v2.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:t41232
psql -h localhost -U postgres

Built from patchset v14 (message #14), July 28, 2026 at 02:55 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 t41232_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 t41232_14 && git checkout t41232_14

Patchset v14 (message #14) is on t41232_14