CI history

  • #24Feb 11, 2022Bharath Rupireddy
  • #22Feb 10, 2022Bharath Rupireddy
  • #20Oct 21, 2021Bharath Rupireddy
  • #1Oct 05, 2021Bharath Rupireddy
  • #24Feb 11, 2022
    v3-0001-add-vcregress-taptest-and-mention-about-Windows-o.patch
  • #22Feb 10, 2022
    v2-0001-add-vcregress-taptest-and-mention-about-Windows-o.patch
  • #20Oct 21, 2021
    v1-0001-add-vcregress-taptest-and-mention-about-Windows-o.patch
  • #1Oct 05, 2021
    v1-0001-add-subscriptioncheck-option-for-vcregress-for-ms.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:t44908
psql -h localhost -U postgres

Built from patchset v24 (message #24), July 27, 2026 at 03:21 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 t44908_24 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 t44908_24 && git checkout t44908_24

Patchset v24 (message #24) is on t44908_24