CI history

  • #9Sep 18, 12:00Yugo Nagata
  • #8Sep 18, 02:13shihao zhong
  • #7Jul 27, 05:36Yugo Nagata
  • #5Sep 30, 2025Yugo Nagata
  • #3Jun 27, 2025Yugo Nagata
  • #9Sep 18, 12:00
    v4-0001-doc-Mention-that-JIT-inlining-does-not-work-with-.patch
  • #8Sep 18, 02:13
    v3_fix_doc_jit_meson.patch
  • #7Jul 27, 05:36
    v2_fix_doc_jit_meson.patch
  • #5Sep 30, 2025
    v2_fix_doc_jit_meson.patch
  • #3Jun 27, 2025
    fix_doc_jit_meson.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.

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

Built from patchset v9 (message #9), November 22, 2026 at 12:14 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 t51635_9 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 t51635_9 && git checkout t51635_9

Patchset v9 (message #9) is on t51635_9