CI history

  • #82Jun 13, 2017Peter Eisentraut
  • #78Jun 01, 2017Andres Freund
  • #47May 10, 2017Peter Eisentraut
  • #20Apr 28, 2017Michael Paquier
  • #3Apr 25, 2017Michael Paquier
  • #82Jun 13, 2017
    0001-Use-RangeVarGetRelidExtended-in-AlterSequence.patch
  • #78Jun 01, 2017
    0001-Make-ALTER-SEQUENCE-including-RESTART-fully-transact.patch
    0002-Modify-sequence-catalog-tuple-before-invoking-post-a.patch
  • #47May 10, 2017
    0001-Add-isolation-tests-for-sequences.patch
    0002-Fix-ALTER-SEQUENCE-locking.patch
    + 1 more
  • #20Apr 28, 2017
    alter-seq-lock-v2.patch
  • #3Apr 25, 2017
    alter-seq-lock.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:t36576
psql -h localhost -U postgres

Built from patchset v82 (message #82), August 18, 2026 at 05:12 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 t36576_82 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 t36576_82 && git checkout t36576_82

Patchset v82 (message #82) is on t36576_82