CI history

  • #134Nov 29, 2019vignesh Cfix on top of #130LLM analysis, 100% sure
  • #130Nov 28, 2019vignesh Crest of #128 after a partial commitLLM analysis, 100% sure
  • #128Nov 27, 2019vignesh Csmall revision of #126LLM analysis, 100% sure
  • #126Nov 25, 2019vignesh Csmall revision of #123LLM analysis, 100% sure
  • #123Nov 24, 2019vignesh Csmall revision of #120LLM analysis, 100% sure
  • #120Nov 22, 2019vignesh Csmall revision of #115LLM analysis, 99% sure
  • #115Nov 18, 2019Pavel Stehulenew seriesLLM analysis, 99% sure
  • #111Nov 18, 2019Amit Kapilasmall revision of #108LLM analysis, 100% sure
  • #108Nov 16, 2019Pavel Stehulesmall revision of #106LLM analysis, 100% sure
  • #106Nov 15, 2019Pavel Stehulesmall revision of #100LLM analysis, 100% sure
  • #100Nov 13, 2019Pavel Stehulerest of #43 after a partial commitLLM analysis, 88% sure
  • #97Nov 12, 2019Amit Kapilasmall revision of #95LLM analysis, 100% sure
  • #95Nov 11, 2019Amit Kapilarebase of #90LLM analysis, 100% sure
  • #90Nov 08, 2019Amit Kapilasmall revision of #77LLM analysis, 100% sure
  • #81Nov 02, 2019Pavel Stehulereworked version of #77LLM analysis, 100% sure
  • #77Oct 24, 2019Amit Kapilasmall revision of #75LLM analysis, 100% sure
  • #75Oct 22, 2019Pavel Stehulesmall revision of #71LLM analysis, 100% sure
  • #71Oct 21, 2019Pavel Stehulesmall revision of #66LLM analysis, 100% sure
  • #66Oct 19, 2019Pavel Stehulesmall revision of #62LLM analysis, 100% sure
  • #62Oct 04, 2019Pavel Stehulesmall revision of #59LLM analysis, 100% sure
  • #59Oct 02, 2019Pavel Stehulesmall revision of #54LLM analysis, 100% sure
  • #54Sep 26, 2019Pavel Stehulesmall revision of #51LLM analysis, 100% sure
  • #51Sep 26, 2019Pavel Stehulesmall revision of #43LLM analysis, 99% sure
  • #43Sep 21, 2019Pavel Stehulesmall revision of #37LLM analysis, 100% sure
  • #37Sep 18, 2019Pavel Stehulesmall revision of #29LLM analysis, 100% sure
  • #29Sep 17, 2019Pavel Stehulereworked version of #21LLM analysis, 100% sure
  • #21Jul 08, 2019Pavel Stehulesmall revision of #19LLM analysis, 100% sure
  • #19Jun 26, 2019Pavel Stehulerebase of #10LLM analysis, 99% sure
  • #10Mar 10, 2019Filip Rembiałkowskismall revision of #8LLM analysis, 100% sure
  • #8Mar 05, 2019Filip Rembiałkowskismall revision of #2LLM analysis, 99% sure
  • #2Dec 18, 2018Pavel Stehulenew seriesLLM analysis, 99% sure
  • #1Dec 18, 2018Filip Rembiałkowskinew seriesLLM analysis, 100% sure
  • #134Nov 29, 2019
    0001-Drop-db-test-chomp-build-farm-failure-fix.patch
  • #130Nov 28, 2019
    0001-Add-tests-for-the-support-of-f-option-in-dropdb-util.patch
  • #128Nov 27, 2019
    0002-Add-tests-for-the-support-of-f-option-in-dropdb-util.patch
    0001-Made-pump_until-usable-as-a-common-subroutine.patch
  • #126Nov 25, 2019
    0002-Made-pump_until-usable-as-a-common-subroutine.patch
    0001-Add-tests-for-the-support-of-drop-database-forcefull.patch
  • #123Nov 24, 2019
    0001-Add-tests-for-the-support-of-f-option-in-dropdb-util.patch
    0002-Made-pump_until-usable-as-a-common-subroutine.patch
  • #120Nov 22, 2019
    0001-Add-tests-for-the-support-of-f-option-in-dropdb-util.patch
    0002-Made-pump_until-usable-as-a-common-subroutine.patch
  • #119Nov 21, 2019
    dropdb-force.pl-patch
  • #115Nov 18, 2019
    dropdb-force2.patch
  • #111Nov 18, 2019
    dropdb-f-20191118.amit.patch
  • #108Nov 16, 2019
    dropdb-f-20191116.patch
  • #106Nov 15, 2019
    dropdb-f-20191115.patch
  • #100Nov 13, 2019
    dropdb-f.patch
  • #97Nov 12, 2019
    drop-database-force-20191112.amit.patch
  • #95Nov 11, 2019
    drop-database-force-20191111.amit.patch
  • #90Nov 08, 2019
    drop-database-force-20191108.amit.patch
  • #81Nov 02, 2019
    drop-database-force-20191102.amit.patch
  • #77Oct 24, 2019
    drop-database-force-20191024.amit.patch
  • #75Oct 22, 2019
    drop-database-force-20191022.patch
  • #71Oct 21, 2019
    drop-database-force-20191021.patch
  • #66Oct 19, 2019
    drop-database-force-20191019.patch
  • #62Oct 04, 2019
    drop-database-force-20191004.patch
  • #59Oct 02, 2019
    drop-database-force-20191002.patch
  • #54Sep 26, 2019
    drop-database-force-20190926-2.patch
  • #51Sep 26, 2019
    drop-database-force-20190926.patch
  • #43Sep 21, 2019
    drop-database-force-20190921-1.patch
  • #37Sep 18, 2019
    drop-database-force-20190918-1.patch
  • #29Sep 17, 2019
    drop-database-force-20190917-1.patch
  • #21Jul 08, 2019
    drop-database-force-20190708.patch
  • #19Jun 26, 2019
    drop-database-force-20190626_01.patch
  • #10Mar 10, 2019
    drop-database-force-20190310_01.patch
  • #8Mar 05, 2019
    drop-database-force-20190305_01.patch
  • #2Dec 18, 2018
    drop-database-force-10.patch
  • #1Dec 18, 2018
    postgresql-dropdb--force.20181218_01.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:t39853
psql -h localhost -U postgres

Built from patchset v134 (message #134), August 18, 2026 at 04:31 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 t39853_134 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 t39853_134 && git checkout t39853_134

Patchset v134 (message #134) is on t39853_134