CI history

  • #7Dec 28, 2021Jelte Fennema-Niosmall revision of #5LLM analysis, 100% sure
  • #5Oct 01, 2021Jelte Fennema-Niosmall revision of #3LLM analysis, 96% sure
  • #3Sep 30, 2021Jelte Fennema-Niosmall revision of #1LLM analysis, 100% sure
  • #1Sep 30, 2021Jelte Fennema-Nionew seriesLLM analysis, 100% sure
  • #7Dec 28, 2021
    0001-Treat-ETIMEDOUT-as-indicating-a-non-recoverable-conn.patch
  • #5Oct 01, 2021
    0001-Consider-ETIMEDOUT-a-connection-failure-when-TCP_USE.patch
  • #3Sep 30, 2021
    0001-Consider-ETIMEDOUT-a-connection-failure.patch
  • #1Sep 30, 2021
    0001-Consider-ETIMEDOUT-a-connection-failure.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:t44879
psql -h localhost -U postgres

Built from patchset v7 (message #7), August 18, 2026 at 03:55 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 t44879_7 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 t44879_7 && git checkout t44879_7

Patchset v7 (message #7) is on t44879_7