CI history

  • #5Mar 20, 2024Daniel Gustafsson
  • #3Feb 28, 2024Daniel Gustafsson
  • #1Feb 23, 2024Daniel Gustafsson
  • #5Mar 20, 2024
    v3-0002-Explicitly-require-password-for-SCRAM-exchange.patch
    v3-0001-Refactor-SASL-exchange-to-return-tri-state-status.patch
  • #3Feb 28, 2024
    v2-0001-Refactor-SASL-exchange-to-return-tri-state-status.patch
    v2-0002-Explicitly-require-password-for-SCRAM-exchange.patch
  • #1Feb 23, 2024
    v1-0002-Explicitly-require-password-for-SCRAM-exchange.patch
    v1-0001-Refactor-SASL-exchange-to-return-tri-state-status.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:t49235
psql -h localhost -U postgres

Built from patchset v5 (message #5), July 27, 2026 at 11:05 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 t49235_5 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 t49235_5 && git checkout t49235_5

Patchset v5 (message #5) is on t49235_5