CI history

  • #25Apr 01, 2020Bruce Momjiannew seriesLLM analysis, 98% sure
  • #22Mar 19, 2020Fabrízio de Royes Mellonew seriesLLM analysis, 98% sure
  • #17Mar 15, 2020Justin Pryzbyfix on top of #6LLM analysis, 100% sure
  • #6Mar 07, 2020Peter Eisentrautrebase of #5LLM analysis, 100% sure
  • #5Feb 21, 2020Peter Eisentrautreworked version of #1LLM analysis, 100% sure
  • #1Feb 13, 2020Peter Eisentrautnew seriesLLM analysis, 100% sure
  • #25Apr 01, 2020
    wal.diff
  • #22Mar 19, 2020
    fix-file-fdw-doc-csvlog.patch
  • #17Mar 15, 2020
    v1-0001-Fix-previous-commit.patch
    v1-0002-Include-the-leader-PID-in-logfile.patch
  • #6Mar 07, 2020
    v3-0001-Refactor-ps_status.c-API.patch
    v3-0002-Unify-several-ways-to-tracking-backend-type.patch
    + 2 more
  • #5Feb 21, 2020
    v2-0001-Refactor-ps_status.c-API.patch
    v2-0002-Unify-several-ways-to-tracking-backend-type.patch
    + 2 more
  • #1Feb 13, 2020
    0001-Add-backend-type-placeholder-to-log_line_prefix.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:t41932
psql -h localhost -U postgres

Built from patchset v25 (message #25), August 18, 2026 at 04:24 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 t41932_25 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 t41932_25 && git checkout t41932_25

Patchset v25 (message #25) is on t41932_25