CI history

  • #13Jul 14, 2020Mark Dilgersmall revision of #5LLM analysis, 98% sure
  • #5Jul 02, 2020Mark Dilgernew seriesLLM analysis, 99% sure
  • #4Jul 01, 2020Mark Dilgerrebase of #1LLM analysis, 100% sure
  • #1Jun 03, 2020Mark Dilgernew seriesLLM analysis, 100% sure
  • #13Jul 14, 2020
    v3-0001-Refactoring-relkind-handling.patch
  • #5Jul 02, 2020
    v2-0002-Refactoring-relkind-handling.patch
  • #4Jul 01, 2020
    v2-0001-Renaming-relkind-as-objtype-where-appropriate.patch
  • #1Jun 03, 2020
    v1-0001-Renaming-relkind-as-objtype-where-appropriate.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:t42460
psql -h localhost -U postgres

Built from patchset v13 (message #13), August 18, 2026 at 04:22 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 t42460_13 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 t42460_13 && git checkout t42460_13

Patchset v13 (message #13) is on t42460_13