CI history

  • #43Mar 06, 2019Chris Traverssmall revision of #40LLM analysis, 99% sure
  • #40Jan 23, 2019Chris Traverssmall revision of #27LLM analysis, 100% sure
  • #35Jan 17, 2019Chris Traversreworked version of #27LLM analysis, 99% sure
  • #27Oct 01, 2018Chris Traversreworked version of #1LLM analysis, 93% sure
  • #16Sep 25, 2018Michael Paquiernew seriesLLM analysis, 99% sure
  • #1Sep 20, 2018Chris Traversnew seriesLLM analysis, 100% sure
  • #43Mar 06, 2019
    signal_readme.patch
  • #40Jan 23, 2019
    signal_readme_patch.diff
  • #35Jan 17, 2019
    signal-comments.patch
  • #27Oct 01, 2018
    sig_doc_patch.patch
  • #16Sep 25, 2018
    pending-sig-atomic.patch
  • #1Sep 20, 2018
    sig_refactor.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.

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

Built from patchset v43 (message #43), November 22, 2026 at 03:24 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 t39383_43 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 t39383_43 && git checkout t39383_43

Patchset v43 (message #43) is on t39383_43