CI history

  • #8Nov 12, 21:07Corey Huinkerrest of #5 after a partial commitLLM analysis, 95% sure
  • #5Nov 11, 01:54Corey Huinkernew seriesLLM analysis, 100% sure
  • #8Nov 12, 21:07
    v19842.2-0001-Decouple-range_bounds_histogram-requirement.patch
    v19842.2-0002-pg_dump-Map-mismatched-NULL-values-arrays-t.patch
    + 1 more
  • #5Nov 11, 01:54
    v2-0001-Allow-empty-arrays-as-input-for-pg_restore_attrib.patch
    v2-0002-Decouple-range_bounds_histogram-requirement-from-.patch
    + 1 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 retrysuccessCI history

This thread has been committed, so CI has stopped here. Anything below is the last result it produced.

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:t254608
psql -h localhost -U postgres

Built from patchset v8 (message #8), November 12, 2026 at 09:19 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 t254608_8 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 t254608_8 && git checkout t254608_8

Patchset v8 (message #8) is on t254608_8