CI history

  • #180Apr 06, 2018Heikki Linnakangas
  • #178Apr 05, 2018Heikki Linnakangas
  • #177Apr 03, 2018Claudio Freire
  • #173Mar 16, 2018Claudio Freire
  • #171Feb 09, 2018Claudio Freire
  • #162Feb 08, 2018Claudio Freire
  • #158Feb 07, 2018Claudio Freire
  • #156Feb 06, 2018Claudio Freire
  • #146Jan 17, 2018Claudio Freire
  • #140Oct 02, 2017Claudio Freire
  • #137Jul 14, 2017Claudio Freire
  • #133Jul 11, 2017Claudio Freire
  • #132Jul 10, 2017Claudio Freire
  • #127Apr 20, 2017Claudio Freire
  • #119Apr 08, 2017Claudio Freire
  • #111Mar 29, 2017Claudio Freire
  • #109Feb 01, 2017Claudio Freire
  • #104Jan 31, 2017Claudio Freire
  • #102Jan 25, 2017Claudio Freire
  • #100Jan 23, 2017Claudio Freire
  • #96Jan 20, 2017Alvaro Herrera
  • #92Dec 28, 2016Claudio Freire
  • #82Dec 22, 2016Claudio Freire
  • #73Nov 17, 2016Claudio Freire
  • #70Oct 26, 2016Claudio Freire
  • #60Sep 15, 2016Claudio Freire
  • #44Sep 14, 2016Pavan Deolasee
  • #37Sep 09, 2016Masahiko Sawada
  • #27Sep 07, 2016Simon Riggs
  • #23Sep 06, 2016Claudio Freire
  • #5Sep 05, 2016Claudio Freire
  • #2Sep 04, 2016Simon Riggs
  • #1Sep 03, 2016Claudio Freire
  • #181Apr 06, 2018
    vacuumbenchone.sh
    vacuumbenchone-results-on-heikkis-laptop.tar.gz
  • #180Apr 06, 2018
    vacuum-tidmap-2.patch
    vacuumbench.sh
  • #179Apr 05, 2018
    vacuumbench.sh
  • #178Apr 05, 2018
    vacuum-tidmap-1.patch
  • #177Apr 03, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v20.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v11.patch
  • #173Mar 16, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v19.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v10.patch
  • #171Feb 09, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v18.patch
  • #166Feb 08, 2018
    calciter.pl
  • #162Feb 08, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v17.patch
  • #158Feb 07, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v16.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v9.patch
  • #156Feb 06, 2018
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v8.patch
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v15.patch
  • #146Jan 17, 2018
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v14.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v7.patch
  • #140Oct 02, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v13.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v6.patch
  • #137Jul 14, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v12.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v5.patch
  • #133Jul 11, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v11.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v4.patch
    + 4 more
  • #132Jul 10, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v11.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v4.patch
    + 6 more
  • #127Apr 20, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v10.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v3.patch
  • #119Apr 08, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v9.patch
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible-v2.patch
  • #111Mar 29, 2017
    0003-Vacuum-free-dead-tuples-array-as-early-as-possible.patch
  • #109Feb 01, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v8.patch
  • #104Jan 31, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v7.patch
  • #102Jan 25, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v6.patch
  • #100Jan 23, 2017
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v5.patch
  • #96Jan 20, 2017
    0001-Prefetch-blocks-during-lazy-vacuum-s-truncation-scan.patch
  • #92Dec 28, 2016
    0001-Vacuum-prefetch-buffers-on-backward-scan-v4.patch
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v4.patch
  • #82Dec 22, 2016
    0001-Vacuum-prefetch-buffers-on-backward-scan-v3.patch
    0002-Vacuum-allow-using-more-than-1GB-work-mem-v3.patch
  • #73Nov 17, 2016
    0002-Vacuum-allow-using-more-than-1GB-work-mem.patch
  • #70Oct 26, 2016
    vacuum_bench_results.tar.gz
    0001-Vacuum-prefetch-buffers-on-backward-scan.patch
    + 2 more
  • #60Sep 15, 2016
    0001-Vacuum-allow-using-more-than-1GB-work-mem-v2-multiarray.patch
  • #44Sep 14, 2016
    vacuum_print_offset_stats.patch
    image (29).png
  • #37Sep 09, 2016
    0001-Collect-dead-tuple-location-as-a-bitmap.patch
  • #27Sep 07, 2016
    vacuum_mem_estimate.v1.patch
  • #23Sep 06, 2016
    0002-Vacuum-prefetch-buffers-on-backward-scan.patch
  • #5Sep 05, 2016
    0001-Vacuum-allow-using-more-than-1GB-work-mem.patch
    0002-Vacuum-free-dead_tuples-sooner.patch
  • #2Sep 04, 2016
    allow_vacuum_work_mem_gt_1GB.v2.patch
  • #1Sep 03, 2016
    0001-Vacuum-allow-using-more-than-1GB-work-mem.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:t35217
psql -h localhost -U postgres

Built from patchset v180 (message #180), August 18, 2026 at 04:55 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 t35217_180 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 t35217_180 && git checkout t35217_180

Patchset v180 (message #180) is on t35217_180