CI history

  • #36Mar 31, 2017Pavel Stehule
  • #33Mar 30, 2017Pavel Stehule
  • #32Mar 30, 2017Surafel Temesgen
  • #28Mar 27, 2017Pavel Stehule
  • #27Mar 26, 2017Pavel Stehule
  • #26Mar 25, 2017Surafel Temesgen
  • #18Mar 15, 2017Pavel Stehule
  • #17Mar 14, 2017Surafel Temesgen
  • #14Mar 11, 2017Pavel Stehule
  • #11Mar 10, 2017Surafel Temesgen
  • #8Mar 09, 2017Surafel Temesgen
  • #5Feb 16, 2017Surafel Temesgen
  • #36Mar 31, 2017
    corresponding_clause_v12.patch
  • #33Mar 30, 2017
    corresponding_clause_v11.patch
  • #32Mar 30, 2017
    corresponding_clause_v10.patch
  • #28Mar 27, 2017
    corresponding_clause_v9.patch
  • #27Mar 26, 2017
    corresponding_clause_v8.patch
  • #26Mar 25, 2017
    corresponding_clause_v7.patch
  • #18Mar 15, 2017
    corresponding_clause_v6.patch
  • #17Mar 14, 2017
    corresponding_clause_v5.patch
  • #14Mar 11, 2017
    corresponding_clause_v4.patch
  • #11Mar 10, 2017
    corresponding_clause_v3.patch
  • #8Mar 09, 2017
    corresponding_clause_v2.patch
  • #5Feb 16, 2017
    corresponding_clause_v1.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:t35867
psql -h localhost -U postgres

Built from patchset v36 (message #36), July 28, 2026 at 07:32 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 t35867_36 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 t35867_36 && git checkout t35867_36

Patchset v36 (message #36) is on t35867_36