CI history

  • #16Jan 27, 2023David Geier
  • #7Jun 27, 2022David Geier
  • #6Apr 12, 2021Luc Vlaming
  • #3Dec 30, 2020Luc Vlaming
  • #1Dec 28, 2020Luc Vlaming
  • #16Jan 27, 2023
    0001-Cache-modules-in-JIT-inlining.patch
  • #8Jun 27, 2022
    go_api_metadata_pg_query.sql
  • #7Jun 27, 2022
    0001-Lazily-JIT.patch
  • #6Apr 12, 2021
    v3-0002-Do-not-generate-the-IR-code-ahead-of-time-but-laz.patch
    v3-0001-Improve-jitting-performance-by-not-emitting-the.patch
  • #3Dec 30, 2020
    jit_partitions.sql
    v2-0001-improve-jitting-performance-somewhat.patch
    + 1 more
  • #1Dec 28, 2020
    jit_partitions.sql
    v1-0001-generate-JIT-IR-code-lazily.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:t43463
psql -h localhost -U postgres

Built from patchset v16 (message #16), July 28, 2026 at 01:13 AM.

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 t43463_16 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 t43463_16 && git checkout t43463_16

Patchset v16 (message #16) is on t43463_16