CI history

  • #57Nov 03, 04:20Hayato Kuroda (Fujitsu)small revision of #55LLM analysis, 100% sure
  • #55Nov 02, 04:47Hayato Kuroda (Fujitsu)reworked version of #53LLM analysis, 96% sure
  • #53Oct 30, 12:37Hayato Kuroda (Fujitsu)small revision of #52LLM analysis, 99% sure
  • #52Oct 30, 10:33Hayato Kuroda (Fujitsu)new seriesLLM analysis, 93% sure
  • #48Oct 08, 01:09Masahiko Sawadafix on top of #43LLM analysis, 100% sure
  • #43Oct 06, 05:46Masahiko Sawadasmall revision of #41LLM analysis, 100% sure
  • #41Oct 05, 22:26Masahiko Sawadaresend of #34LLM analysis, 99% sure
  • #34Sep 25, 22:24Masahiko Sawadasmall revision of #29LLM analysis, 99% sure
  • #31Sep 25, 09:28shveta malikfix on top of #29LLM analysis, 100% sure
  • #29Sep 24, 22:08Masahiko Sawadasmall revision of #25LLM analysis, 99% sure
  • #25Sep 22, 20:15Masahiko Sawadareworked version of #24LLM analysis, 100% sure
  • #24Sep 22, 06:32Nikolay Samokhvalovnew seriesLLM analysis, 99% sure
  • #19Jul 30, 21:48Masahiko Sawadafix on top of #16LLM analysis, 98% sure
  • #16Jul 30, 07:06Masahiko Sawadasmall revision of #13LLM analysis, 100% sure
  • #15Jul 29, 10:21Amit Kapilafix on top of #13LLM analysis, 100% sure
  • #14Jul 29, 05:28Amit Kapilafix on top of #13LLM analysis, 94% sure
  • #13Jul 27, 16:39Masahiko Sawadarest of #4 after a partial commitLLM analysis, 100% sure
  • #4Jul 16, 01:21Masahiko Sawadasmall revision of #3LLM analysis, 97% sure
  • #3Jul 14, 21:02Masahiko Sawadasmall revision of #2LLM analysis, 100% sure
  • #2Jul 10, 04:22Srinath Reddy Sadipirallaresend of #1LLM analysis, 100% sure
  • #1Jul 10, 04:18Srinath Reddy Sadipirallanew seriesLLM analysis, 100% sure
  • #57Nov 03, 04:20
    v3-0001-Stabilize-051_effective_wal_level.patch
    v3-0002-Ensure-injection-point-repack-concurrently-before.patch
    + 1 more
  • #55Nov 02, 04:47
    v2-0001-Stabilize-051_effective_wal_level.patch
    v2-0002-Ensure-injection-point-repack-concurrently-before.patch
    + 1 more
  • #53Oct 30, 12:37
    0001-Stabilize-051_effective_wal_level.patch
    0002-Ensure-injection-point-repack-concurrently-before-lo.patch
    + 1 more
  • #52Oct 30, 10:33
    add_wait.diff
  • #48Oct 08, 01:09
    v1-0001-Stabilize-recently-added-tests-in-051_effective_w.patch
  • #43Oct 06, 05:46
    v5-0001-Add-an-init-callback-for-the-logical-decoding-con.patch
    v5-0002-Fix-slotsync-when-logical-decoding-is-disabled-an.patch
  • #41Oct 05, 22:26
    v4-0001-Add-an-init-callback-for-the-logical-decoding-con.patch
    v4-0002-Fix-slotsync-when-logical-decoding-is-disabled-an.patch
  • #34Sep 25, 22:24
    v3-0002-Fix-slotsync-when-logical-decoding-is-disabled-an.patch
    v3-0001-Add-an-init-callback-for-the-logical-decoding-con.patch
  • #31Sep 25, 09:28
    0001-comment-change.patch.txt
  • #29Sep 24, 22:08
    v2-0001-Fix-slotsync-when-logical-decoding-is-disabled-an.patch
  • #25Sep 22, 20:15
    v1-0001-Fix-slotsync-when-logical-decoding-is-disabled-an.patch
  • #24Sep 22, 06:32
    v1-0001-fix-slotsync-logical-decoding-status-aba.patch
  • #19Jul 30, 21:48
    0001-Fix-background-psql-session-cleanup-in-051_effective.patch
  • #16Jul 30, 07:06
    v5-0001-Fix-races-between-deactivation-of-logical-decodin.patch
  • #15Jul 29, 10:21
    v4_topup_comment-fixup.patch
    051_effective_wal_level_standby5.log
    + 1 more
  • #14Jul 29, 05:28
    v1_fix_comments_1.patch
  • #13Jul 27, 16:39
    v4-0001-Fix-races-between-deactivation-of-logical-decodin.patch
  • #4Jul 16, 01:21
    v3-0002-Fix-races-between-deactivation-of-logical-decodin.patch
    v3-0001-Fix-race-condition-when-enabling-logical-decoding.patch
  • #3Jul 14, 21:02
    v2-0001-Fix-race-condition-when-enabling-logical-decoding.patch
  • #2Jul 10, 04:22
    v1-0001-Avoid-writing-a-redundant-logical-decoding-status-ch.patch
  • #1Jul 10, 04:18
    v1-0001-Avoid-writing-a-redundant-logical-decoding-status-ch.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:t253038
psql -h localhost -U postgres

Built from patchset v57 (message #57), November 05, 2026 at 04:35 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 t253038_57 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 t253038_57 && git checkout t253038_57

Patchset v57 (message #57) is on t253038_57