CI history

  • #25Feb 01, 2017Michael Paquier
  • #21Nov 22, 2016Michael Paquier
  • #12Sep 07, 2016Michael Paquier
  • #8Sep 02, 2016Michael Paquier
  • #2Aug 23, 2016Michael Paquier
  • #1Aug 12, 2016Michael Paquier
  • #25Feb 01, 2017
    0001-Forbid-newline-and-carriage-return-characters-in-dat.patch
    0002-Ensure-clean-up-of-data-directory-even-with-restrict.patch
  • #21Nov 22, 2016
    0002-Ensure-clean-up-of-data-directory-even-with-restrict.patch
    0001-Forbid-newline-and-carriage-return-characters-in-dat.patch
  • #12Sep 07, 2016
    0001-Forbid-newline-and-carriage-return-characters-in-dat.patch
    0002-Ensure-clean-up-of-data-directory-even-with-restrict.patch
  • #8Sep 02, 2016
    forbid-cr-lf-v3.patch
  • #2Aug 23, 2016
    forbid-cr-lf-v2.patch
  • #1Aug 12, 2016
    forbid-cr-lf.patch
    createddl.pl

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

Built from patchset v25 (message #25), July 28, 2026 at 08:28 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 t35070_25 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 t35070_25 && git checkout t35070_25

Patchset v25 (message #25) is on t35070_25