CI history

  • #6Aug 04, 15:11Fujii Masaosmall revision of #5LLM analysis, 100% sure
  • #5Jul 17, 22:38Chao Lismall revision of #2LLM analysis, 100% sure
  • #2Jul 17, 09:00Ian Lawrence Barwicksmall revision of #1LLM analysis, 100% sure
  • #1Jul 17, 05:37Chao Linew seriesLLM analysis, 100% sure
  • #6Aug 04, 15:11
    v4-0001-doc-Clarify-wal_sender_shutdown_timeout-values.patch
  • #5Jul 17, 22:38
    v3-0001-doc-Clarify-wal_sender_shutdown_timeout-behavior-.patch
  • #2Jul 17, 09:00
    v2-0001-doc-improve-description-for-wal_sender_shutdown_t.patch
  • #1Jul 17, 05:37
    v1-0001-doc-Clarify-wal_sender_shutdown_timeout-behavior-.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

This thread has been committed, so CI has stopped here. Anything below is the last result it produced.

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

Built from patchset v6 (message #6), August 04, 2026 at 03: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 t253101_6 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 t253101_6 && git checkout t253101_6

Patchset v6 (message #6) is on t253101_6