CI history

  • #16Sep 17, 01:07shihao zhongsmall revision of #14LLM analysis, 100% sure
  • #14Sep 15, 08:38Bharath Rupireddyreworked version of #10LLM analysis, 93% sure
  • #11Sep 13, 18:37Nikolay Samokhvalovfix on top of #10LLM analysis, 100% sure
  • #10Sep 08, 16:49Bharath Rupireddysmall revision of #8LLM analysis, 100% sure
  • #8Sep 07, 19:15Bharath Rupireddyreworked version of #5LLM analysis, 100% sure
  • #5Aug 31, 18:14Bharath Rupireddysmall revision of #3LLM analysis, 100% sure
  • #3Aug 28, 20:20Bharath Rupireddynew seriesLLM analysis, 100% sure
  • #16Sep 17, 01:07
    v6-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.patch
    v6-0002-Detect-premature-exit-of-the-REPACK-decoding-work.patch
    + 2 more
  • #14Sep 15, 08:38
    v5-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.patch
    v5-0002-Detect-premature-exit-of-the-REPACK-decoding-work.patch
    + 2 more
  • #11Sep 13, 18:37
    0001-repack-worker-post-attachment-exit-minimal.patch
  • #10Sep 08, 16:49
    v4-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.patch
  • #8Sep 07, 19:15
    v3-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.patch
  • #5Aug 31, 18:14
    v2-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.patch
    v2-0002-Fix-repack-decoding-worker-startup-wait-event.patch
  • #3Aug 28, 20:20
    v1-0001-Fix-hang-and-deadlock-in-concurrent-REPACK-worker.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:t253577
psql -h localhost -U postgres

Built from patchset v16 (message #16), September 17, 2026 at 01:17 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 t253577_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 t253577_16 && git checkout t253577_16

Patchset v16 (message #16) is on t253577_16