CI history

  • #23Apr 08, 2022Nathan Bossart
  • #11Nov 10, 2021Nathan Bossart
  • #10Oct 08, 2021Nathan Bossart
  • #7Sep 14, 2021Nathan Bossart
  • #6Aug 31, 2021Nathan Bossart
  • #5Aug 06, 2021Nathan Bossart
  • #4Jul 09, 2021Nathan Bossart
  • #2Jun 07, 2021Nathan Bossart
  • #23Apr 08, 2022
    v8-0001-Move-WAL-segment-creation-logic-to-its-own-functi.patch
    v8-0002-WAL-segment-pre-allocation.patch
  • #11Nov 10, 2021
    v7-0001-Move-WAL-segment-creation-logic-to-its-own-functi.patch
    v7-0002-WAL-segment-pre-allocation.patch
  • #10Oct 08, 2021
    v6-0002-WAL-segment-pre-allocation.patch
    v6-0001-Move-WAL-segment-creation-logic-to-its-own-functi.patch
  • #7Sep 14, 2021
    v5-0001-wal-segment-pre-allocation.patch
  • #6Aug 31, 2021
    v4-0001-wal-segment-pre-allocation.patch
  • #5Aug 06, 2021
    v3-0001-wal-segment-pre-allocation.patch
  • #4Jul 09, 2021
    v2-0001-wal-segment-pre-allocation.patch
  • #2Jun 07, 2021
    v1-0001-wal-segment-pre-allocation.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:t43456
psql -h localhost -U postgres

Built from patchset v23 (message #23), July 27, 2026 at 02:57 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 t43456_23 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 t43456_23 && git checkout t43456_23

Patchset v23 (message #23) is on t43456_23