CI history

  • #39Feb 17, 2021Takashi Menjo
  • #38Aug 04, 2020Takashi Menjo
  • #35Jan 30, 2019Takashi Menjo
  • #32Jan 25, 2019Takashi Menjo
  • #29Dec 10, 2018Dmitry Dolgov
  • #1Jan 16, 2018Yoshimi Ichiyanagi
  • #39Feb 17, 2021
    v5-0001-Add-configure-option-for-PMDK.patch
    v5-0003-Walreceiver-WAL-IO-using-PMDK.patch
    + 1 more
  • #38Aug 04, 2020
    v4-0001-Add-configure-option-for-PMDK.patch
    v4-0003-Walreceiver-WAL-IO-using-PMDK.patch
    + 1 more
  • #35Jan 30, 2019
    0001-Add-configure-option-for-PMDK-v3.patch
    0002-Read-write-WAL-files-using-PMDK-v3.patch
    + 1 more
  • #32Jan 25, 2019
    0001-Add-configure-option-for-PMDK-v2.patch
    0002-Read-write-WAL-files-using-PMDK-v2.patch
    + 1 more
  • #29Dec 10, 2018
    0001-Add-configure-option-for-PMDK-v2.patch
    0003-Walreceiver-WAL-IO-using-PMDK-v2.patch
    + 1 more
  • #1Jan 16, 2018
    0002-Read-write-WAL-files-using-PMDK.patch
    0003-Walreceiver-WAL-IO-using-PMDK.patch
    + 1 more

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 retrytests failedCI 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:t38031
psql -h localhost -U postgres

Built from patchset v39 (message #39), July 27, 2026 at 05:40 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 t38031_39 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 t38031_39 && git checkout t38031_39

Patchset v39 (message #39) is on t38031_39