CI history

  • #124Aug 31, 2021Nathan Bossartfix on top of #99LLM analysis, 100% sure
  • #118Aug 31, 2021Nathan Bossartfix on top of #99LLM analysis, 100% sure
  • #99Aug 23, 2021Alvaro Herrerasmall revision of #95LLM analysis, 100% sure
  • #95Aug 20, 2021Alvaro Herrerasmall revision of #93LLM analysis, 100% sure
  • #93Aug 20, 2021Nathan Bossartreworked version of #84LLM analysis, 100% sure
  • #84Aug 20, 2021Alvaro Herrerasmall revision of #83LLM analysis, 100% sure
  • #83Aug 19, 2021Nathan Bossartsmall revision of #82LLM analysis, 100% sure
  • #82Aug 18, 2021Alvaro Herrerasmall revision of #81LLM analysis, 100% sure
  • #81Aug 18, 2021Nathan Bossartsmall revision of #71LLM analysis, 100% sure
  • #71Aug 17, 2021Nathan Bossartsmall revision of #66LLM analysis, 100% sure
  • #66Aug 17, 2021Nathan Bossartsmall revision of #64LLM analysis, 100% sure
  • #64Aug 06, 2021Nathan Bossartsmall revision of #62LLM analysis, 100% sure
  • #62Aug 06, 2021Nathan Bossartsmall revision of #59LLM analysis, 100% sure
  • #59Aug 05, 2021Nathan Bossartsmall revision of #53LLM analysis, 100% sure
  • #53Aug 02, 2021Alvaro Herrerasmall revision of #48LLM analysis, 100% sure
  • #48Jul 30, 2021Alvaro Herrerasmall revision of #41LLM analysis, 99% sure
  • #41Mar 15, 2021Nathan Bossartrebase of #40LLM analysis, 100% sure
  • #40Feb 19, 2021Nathan Bossartsmall revision of #39LLM analysis, 97% sure
  • #39Jan 27, 2021Nathan Bossartrebase of #27LLM analysis, 100% sure
  • #32Dec 18, 2020Kyotaro Horiguchismall revision of #29LLM analysis, 100% sure
  • #29Dec 16, 2020Kyotaro Horiguchismall revision of #28LLM analysis, 100% sure
  • #28Dec 15, 2020Kyotaro Horiguchismall revision of #25LLM analysis, 97% sure
  • #27Dec 14, 2020Nathan Bossartreworked version of #25LLM analysis, 89% sure
  • #25Oct 14, 2020Kyotaro Horiguchismall revision of #17LLM analysis, 96% sure
  • #17Jun 25, 2020Kyotaro Horiguchireworked version of #16LLM analysis, 100% sure
  • #16Jun 19, 2020Matsumura, Ryoreworked version of #13LLM analysis, 98% sure
  • #13Mar 26, 2020Nathan Bossartreworked version of #3LLM analysis, 100% sure
  • #3Dec 13, 2019Nathan Bossartsmall revision of #1LLM analysis, 100% sure
  • #1Dec 12, 2019Nathan Bossartnew seriesLLM analysis, 100% sure
  • #124Aug 31, 2021
    flush-to-boundary.patch
  • #118Aug 31, 2021
    avoid_boundary_race.patch
  • #99Aug 23, 2021
    v15-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #95Aug 20, 2021
    v14-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #93Aug 20, 2021
    v13-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #84Aug 20, 2021
    v12-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #83Aug 19, 2021
    v11-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #82Aug 18, 2021
    v10-0001-Avoid-creating-archive-status-.ready-files-too-e.patch
  • #81Aug 18, 2021
    v9-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #71Aug 17, 2021
    v8-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #66Aug 17, 2021
    v7-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #64Aug 06, 2021
    v6-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #62Aug 06, 2021
    v5-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #59Aug 05, 2021
    v4-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #53Aug 02, 2021
    v3-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #48Jul 30, 2021
    v2-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
  • #41Mar 15, 2021
    v2-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
    v2-0002-Keep-track-of-notified-ready-for-archive-position.patch
  • #40Feb 19, 2021
    v1-0001-Avoid-creating-archive-status-.ready-files-too-ea.patch
    v1-0002-Keep-track-of-notified-ready-for-archive-position.patch
  • #39Jan 27, 2021
    0001-WIP-Avoid-marking-segments-as-ready-for-archival-too.patch
  • #32Dec 18, 2020
    v5-0001-Avoid-archiving-a-WAL-segment-that-continues-to-t.patch
    v5-0002-debug-print.patch
  • #29Dec 16, 2020
    v4-0001-Avoid-archiving-a-WAL-segment-that-continues-to-t.patch
    v4-0002-debug-print.patch
  • #28Dec 15, 2020
    v3-0001-PoC-Avoid-archiving-a-WAL-segment-that-continues-.patch
  • #27Dec 14, 2020
    0001-WIP-Avoid-marking-segments-as-ready-for-archival-too.patch
  • #25Oct 14, 2020
    v2-0001-Avoid-archiving-a-WAL-segment-that-continues-to-t.patch
  • #17Jun 25, 2020
    0001-Avoid-to-archive-immature-records.patch
  • #16Jun 19, 2020
    test_in_primary.sh
    bugfix_early_archiving_v1.0.patch
  • #13Mar 26, 2020
    v3-0001-Avoid-marking-WAL-segments-as-ready-for-archive-t.patch
  • #3Dec 13, 2019
    fix_ready_file_v2.patch
  • #1Dec 12, 2019
    repro_helper.patch
    ready_file_fix.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

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

Built from patchset v124 (message #124), August 18, 2026 at 04:01 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 t41663_124 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 t41663_124 && git checkout t41663_124

Patchset v124 (message #124) is on t41663_124