CI history

  • #24Feb 20, 12:33Daniel Gustafssonfix on top of #23LLM analysis, 96% sure
  • #23Feb 13, 22:32Daniel Gustafssonfix on top of #16LLM analysis, 97% sure
  • #16Mar 17, 2025Jacob Championsmall revision of #12LLM analysis, 100% sure
  • #12Mar 05, 2025Daniel Gustafssonnew seriesLLM analysis, 100% sure
  • #24Feb 20, 12:33
    0001-Ensure-tests-pass-when-FIPS-is-enabled.patch
  • #23Feb 13, 22:32
    0002-doc-Add-note-to-ssl_group-config-on-X25519-and-FIPS.patch
    0001-Avoid-using-the-X25519-curve-in-ssl-tests.patch
  • #16Mar 17, 2025
    v2-0001-Add-x25519-to-the-default-set-of-curves.patch
    v2-0002-squash-Add-x25519-to-the-default-set-of-curves.patch
  • #12Mar 05, 2025
    0001-Add-x25519-to-the-default-set-of-curves.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.

appliesinfra errorCI 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:t49794
psql -h localhost -U postgres

Built from patchset v24 (message #24), November 20, 2026 at 02:23 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 t49794_24 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 t49794_24 && git checkout t49794_24

Patchset v24 (message #24) is on t49794_24