CI history

  • #34Mar 09, 2022Brar Pieningrest of #27 after a partial commitLLM analysis, 97% sure
  • #27Mar 01, 2022Brar Pieningsmall revision of #24LLM analysis, 99% sure
  • #24Feb 28, 2022Brar Pieningsmall revision of #7LLM analysis, 98% sure
  • #7Dec 15, 2021Brar Pieningsmall revision of #1LLM analysis, 100% sure
  • #1Dec 05, 2021Brar Pieningnew seriesLLM analysis, 100% sure
  • #34Mar 09, 2022
    add_section_ids.patch
  • #27Mar 01, 2022
    protocol.sgml-anchors_v4.patch
  • #24Feb 28, 2022
    protocol.sgml-anchors_v3.patch
  • #7Dec 15, 2021
    protocol.sgml-anchors_v2.patch
  • #1Dec 05, 2021
    protocol.sgml-anchors.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:t45202
psql -h localhost -U postgres

Built from patchset v34 (message #34), August 18, 2026 at 03:53 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 t45202_34 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 t45202_34 && git checkout t45202_34

Patchset v34 (message #34) is on t45202_34