CI history

  • #37Jan 16, 2018Peter Eisentraut
  • #35Jan 05, 2018Peter Eisentraut
  • #34Dec 20, 2017Peter Eisentraut
  • #30Dec 06, 2017Peter Eisentraut
  • #26Dec 01, 2017Peter Eisentraut
  • #8Nov 14, 2017Peter Eisentraut
  • #1Oct 31, 2017Peter Eisentraut
  • #37Jan 16, 2018
    v7-0001-Transaction-control-in-PL-procedures.patch
  • #35Jan 05, 2018
    v6-0001-Transaction-control-in-PL-procedures.patch
  • #34Dec 20, 2017
    v5-0001-Transaction-control-in-PL-procedures.patch
  • #30Dec 06, 2017
    v4-0001-Transaction-control-in-PL-procedures.patch
  • #26Dec 01, 2017
    v3-0001-Transaction-control-in-PL-procedures.patch
  • #8Nov 14, 2017
    v2-0001-Transaction-control-in-PL-procedures.patch
  • #1Oct 31, 2017
    v1-0001-Transaction-control-in-PL-Python-procedures.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:t37656
psql -h localhost -U postgres

Built from patchset v37 (message #37), July 27, 2026 at 09:21 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 t37656_37 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 t37656_37 && git checkout t37656_37

Patchset v37 (message #37) is on t37656_37