CI history

  • #6Oct 29, 2019Andres Freundrest of #1 after a partial commitLLM analysis, 100% sure
  • #1Sep 27, 2019Andres Freundnew seriesLLM analysis, 100% sure
  • #6Oct 29, 2019
    v2-0001-jit-Instrument-function-purpose-separately-add-tr.patch
    v2-0002-Refactor-explain.c-to-pass-ExprState-down-to-show.patch
    + 6 more
  • #1Sep 27, 2019
    v1-0001-jit-Instrument-function-purpose-separately-add-tr.patch
    v1-0002-Refactor-explain.c-to-pass-ExprState-down-to-show.patch
    + 10 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 retrytests failedCI 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:t41275
psql -h localhost -U postgres

Built from patchset v6 (message #6), August 18, 2026 at 04:30 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 t41275_6 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 t41275_6 && git checkout t41275_6

Patchset v6 (message #6) is on t41275_6