CI history

  • #13Apr 12, 2018Peter Eisentraut
  • #7Apr 11, 2018Pavan Deolasee
  • #1Apr 10, 2018Pavan Deolasee
  • #13Apr 12, 2018
    0001-Clarify-TOAST-terminology-in-variables-and-error-mes.patch
  • #7Apr 11, 2018
    0002-Do-more-extensive-search-while-looking-for-duplicate.patch
    0001-Do-not-overwrite-the-nextOid-counter-while-replaying.patch
  • #1Apr 10, 2018
    pg_toast_corruption_v3.patch
    toast_corruption.sh

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:t38531
psql -h localhost -U postgres

Built from patchset v13 (message #13), August 18, 2026 at 04:55 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 t38531_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 t38531_13 && git checkout t38531_13

Patchset v13 (message #13) is on t38531_13