CI history

  • #75Mar 01, 2024Jeff Davisnew seriesLLM analysis, 99% sure
  • #55Oct 17, 2023Jeff Davissmall revision of #50LLM analysis, 100% sure
  • #50Oct 11, 2023Jeff Davissmall revision of #45LLM analysis, 98% sure
  • #45Oct 07, 2023Jeff Davisnew seriesLLM analysis, 100% sure
  • #75Mar 01, 2024
    v1-0001-CREATE-DATABASE-.-STRICT_UNICODE.patch
  • #55Oct 17, 2023
    v3-0001-Additional-unicode-primitive-functions.patch
  • #50Oct 11, 2023
    v2-0001-Additional-unicode-primitive-functions.patch
  • #45Oct 07, 2023
    v1-0001-Internal-functions-for-determining-Unicode-genera.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:t48437
psql -h localhost -U postgres

Built from patchset v75 (message #75), August 18, 2026 at 03:10 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 t48437_75 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 t48437_75 && git checkout t48437_75

Patchset v75 (message #75) is on t48437_75