CI history

  • #13Apr 13, 2017Petr Jelinek
  • #6Mar 24, 2017Petr Jelinek
  • #5Mar 21, 2017Petr Jelinek
  • #3Mar 20, 2017Petr Jelinek
  • #2Mar 18, 2017Petr Jelinek
  • #1Mar 07, 2017Petr Jelinek
  • #13Apr 13, 2017
    Add-option-to-modify-sync-commit-per-subscription-v2.patch
  • #6Mar 24, 2017
    0001-Add-option-to-modify-sync-commit-per-subscription.patch
  • #5Mar 21, 2017
    0001-Add-option-to-modify-sync-commit-per-subscription.patch
  • #3Mar 20, 2017
    0001-Add-option-to-modify-sync-commit-per-subscription.patch
  • #2Mar 18, 2017
    0001-Add-option-to-modify-sync-commit-per-subscription.patch
  • #1Mar 07, 2017
    Add-option-to-modify-sync-commit-per-subscription.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:t36193
psql -h localhost -U postgres

Built from patchset v13 (message #13), July 28, 2026 at 07:13 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 t36193_13 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 t36193_13 && git checkout t36193_13

Patchset v13 (message #13) is on t36193_13