CI history

  • #27Nov 27, 2018Sergei Kornilovsmall revision of #26LLM analysis, 100% sure
  • #26Nov 27, 2018Peter Eisentrautreworked version of #19LLM analysis, 98% sure
  • #19Nov 26, 2018Sergei Kornilovsmall revision of #10LLM analysis, 100% sure
  • #10Nov 26, 2018Sergei Kornilovnew seriesLLM analysis, 100% sure
  • #27Nov 27, 2018
    0001-WIP-Only-allow-one-recovery-target-setting-v002.patch
  • #26Nov 27, 2018
    0001-WIP-Only-allow-one-recovery-target-setting.patch
  • #19Nov 26, 2018
    disallow_multiple_recovery_targets_v002.patch
  • #10Nov 26, 2018
    disallow_multiple_recovery_targets_v001.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:t39717
psql -h localhost -U postgres

Built from patchset v27 (message #27), July 28, 2026 at 05:00 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 t39717_27 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 t39717_27 && git checkout t39717_27

Patchset v27 (message #27) is on t39717_27