CI history

  • #76Jun 06, 2022Michael Paquierfix on top of #71LLM analysis, 94% sure
  • #71May 18, 2022Michael Paquiersmall revision of #69LLM analysis, 100% sure
  • #69May 16, 2022Michael Paquierfix on top of #64LLM analysis, 100% sure
  • #64May 09, 2022Michael Paquierfix on top of #45LLM analysis, 99% sure
  • #59Apr 01, 2022Michael Paquierfix on top of #45LLM analysis, 99% sure
  • #45Mar 03, 2022Michael Paquiersmall revision of #41LLM analysis, 100% sure
  • #41Mar 02, 2022Michael Paquierrest of #40 after a partial commitLLM analysis, 100% sure
  • #40Feb 16, 2022Michael Paquierreworked version of #39LLM analysis, 91% sure
  • #39Feb 15, 2022Michael Paquiersmall revision of #29LLM analysis, 96% sure
  • #29Jan 18, 2022Michael Paquiersmall revision of #27LLM analysis, 99% sure
  • #27Jan 11, 2022Michael Paquierrebase of #26LLM analysis, 96% sure
  • #26Jan 05, 2022Michael Paquierrebase of #25LLM analysis, 99% sure
  • #25Dec 16, 2021Michael Paquiersmall revision of #8LLM analysis, 97% sure
  • #8Sep 08, 2021Michael Paquiersmall revision of #6LLM analysis, 90% sure
  • #6May 20, 2021Michael Paquiersmall revision of #1LLM analysis, 94% sure
  • #1May 15, 2021Michael Paquiernew seriesLLM analysis, 100% sure
  • #76Jun 06, 2022
    upgrade-tap-logs.patch
  • #71May 18, 2022
    upgrade-tap-fixes-noah-3.patch
  • #69May 16, 2022
    upgrade-tap-fixes-noah-2.patch
  • #64May 09, 2022
    upgrade-tap-fixes-noah.patch
  • #59Apr 01, 2022
    win32-upgradecheck.patch
  • #45Mar 03, 2022
    v11-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #41Mar 02, 2022
    v10-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #40Feb 16, 2022
    v9-0001-Fix-sanity-check-for-PGHOST-ADDR-in-pg_upgrade-wi.patch
    v9-0002-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #39Feb 15, 2022
    v8-0001-Fix-sanity-check-for-PGHOST-ADDR-in-pg_upgrade-wi.patch
    v8-0002-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #35Feb 13, 2022
    0001-Remove-REGRESS_OUTPUTDIR-environment-variable.not-for-cfbot-patch
  • #29Jan 18, 2022
    v7-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #27Jan 11, 2022
    v6-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #26Jan 05, 2022
    v5-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #25Dec 16, 2021
    v4-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #8Sep 08, 2021
    v3-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #6May 20, 2021
    v2-0001-Switch-tests-of-pg_upgrade-to-use-TAP.patch
  • #1May 15, 2021
    0001-Switch-tests-of-pg_upgrade-to-use-TAP.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:t44230
psql -h localhost -U postgres

Built from patchset v76 (message #76), August 18, 2026 at 03:49 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 t44230_76 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 t44230_76 && git checkout t44230_76

Patchset v76 (message #76) is on t44230_76