CI history

  • #11Jan 11, 2019Peter Eisentrautrest of #7 after a partial commitLLM analysis, 100% sure
  • #9Jan 08, 2019Michael Paquierfix on top of #7LLM analysis, 100% sure
  • #7Dec 28, 2018Peter Eisentrautreworked version of #4LLM analysis, 100% sure
  • #4Dec 27, 2018Peter Eisentrautnew seriesLLM analysis, 100% sure
  • #11Jan 11, 2019
    v3-0002-Change-default-of-recovery_target_timeline-to-lat.patch
  • #9Jan 08, 2019
    timeline-current-test.patch
  • #7Dec 28, 2018
    v2-0001-Add-value-current-for-recovery_target_timeline.patch
    v2-0002-Change-default-of-recovery_target_timeline-to-lat.patch
  • #4Dec 27, 2018
    0001-Always-use-latest-timeline-in-standby-mode.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:t39882
psql -h localhost -U postgres

Built from patchset v11 (message #11), July 28, 2026 at 04:45 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 t39882_11 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 t39882_11 && git checkout t39882_11

Patchset v11 (message #11) is on t39882_11