CI history

  • #131Dec 18, 2018Konstantin Knizhnik
  • #130Oct 25, 2018Konstantin Knizhnik
  • #129Aug 27, 2018Konstantin Knizhnik
  • #52Apr 06, 2018Konstantin Knizhnik
  • #51Apr 06, 2018Konstantin Knizhnik
  • #48Feb 09, 2018Konstantin Knizhnik
  • #27Jan 22, 2018Konstantin Knizhnik
  • #6Jan 19, 2018Konstantin Knizhnik
  • #3Jan 18, 2018Konstantin Knizhnik
  • #1Jan 17, 2018Konstantin Knizhnik
  • #131Dec 18, 2018
    session_pool-12.patch
  • #130Oct 25, 2018
    session_pool-11.patch
  • #129Aug 27, 2018
    session_pool-10.patch
  • #52Apr 06, 2018
    session_pool-8.patch
  • #51Apr 06, 2018
    session_pool-7.patch
  • #48Feb 09, 2018
    session_pool-5.patch
  • #46Feb 02, 2018
    ycsb-zipf-pool.png
  • #27Jan 22, 2018
    session_pool-4.patch
  • #6Jan 19, 2018
    session_pool-3.patch
  • #3Jan 18, 2018
    session_pool-2.patch
  • #1Jan 17, 2018
    session_pool.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 retrytests timeoutCI 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:t38039
psql -h localhost -U postgres

Built from patchset v131 (message #131), July 28, 2026 at 05:09 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 t38039_131 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 t38039_131 && git checkout t38039_131

Patchset v131 (message #131) is on t38039_131