CI history

  • #93Nov 10, 2017Pavel Stehule
  • #92Sep 23, 2017Fabien COELHO
  • #90Sep 06, 2017Fabien COELHO
  • #84Sep 04, 2017Fabien COELHO
  • #75Sep 04, 2017Tom Lane
  • #72Aug 26, 2017Fabien COELHO
  • #70Aug 26, 2017Fabien COELHO
  • #26Apr 02, 2017Fabien COELHO
  • #17Apr 02, 2017Fabien COELHO
  • #16Apr 02, 2017Fabien COELHO
  • #11Apr 02, 2017Fabien COELHO
  • #8Mar 31, 2017Tom Lane
  • #93Nov 10, 2017
    psql-server-version-2.patch
  • #92Sep 23, 2017
    psql-server-version-1.patch.gz
  • #90Sep 06, 2017
    psql-server-version-1.patch
  • #84Sep 04, 2017
    psql-version-num-8.patch
  • #75Sep 04, 2017
    psql-version-num-7.patch
  • #72Aug 26, 2017
    psql-version-num-6.patch
  • #70Aug 26, 2017
    psql-version-num-5.patch
  • #26Apr 02, 2017
    psql-version-num-4.patch
  • #17Apr 02, 2017
    psql-version-num-3.patch
  • #16Apr 02, 2017
    psql-version-num-2.patch
  • #11Apr 02, 2017
    psql-version-num-1.patch
  • #8Mar 31, 2017
    variable-substitution-in-backticks-1.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:t36376
psql -h localhost -U postgres

Built from patchset v93 (message #93), August 18, 2026 at 05:02 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 t36376_93 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 t36376_93 && git checkout t36376_93

Patchset v93 (message #93) is on t36376_93