CI history

  • #19Mar 24, 2017Aleksander Alekseev
  • #13Mar 24, 2017Aleksander Alekseev
  • #10Mar 10, 2017Aleksander Alekseev
  • #6Mar 09, 2017Aleksander Alekseev
  • #3Mar 06, 2017Aleksander Alekseev
  • #19Mar 24, 2017
    partitioning_bottleneck_fix_v4_step1.patch
    partitioning_bottleneck_fix_v4_step2.patch
  • #13Mar 24, 2017
    partitioning_bottleneck_fix_v3_step1.patch
    partitioning_bottleneck_fix_v3_step2.patch
  • #10Mar 10, 2017
    partitioning_bottleneck_fix_v3.patch
  • #6Mar 09, 2017
    partitioning_bottleneck_fix_v2.patch
  • #3Mar 06, 2017
    partitioning_bottleneck_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:t36151
psql -h localhost -U postgres

Built from patchset v19 (message #19), July 28, 2026 at 07:37 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 t36151_19 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 t36151_19 && git checkout t36151_19

Patchset v19 (message #19) is on t36151_19