CI history

  • #16Apr 29, 2025Matheus Alcantarasmall revision of #12LLM analysis, 100% sure
  • #12Apr 25, 2025Matheus Alcantarasmall revision of #10LLM analysis, 93% sure
  • #10Apr 25, 2025Matheus Alcantarasmall revision of #8LLM analysis, 100% sure
  • #8Apr 24, 2025Matheus Alcantarasmall revision of #6LLM analysis, 97% sure
  • #6Apr 23, 2025Matheus Alcantaranew seriesLLM analysis, 100% sure
  • #16Apr 29, 2025
    v5-0001-Make-directory-work-with-extension-control-path.patch
  • #12Apr 25, 2025
    v4-0001-Make-directory-work-with-extension-control-path.patch
  • #10Apr 25, 2025
    v3-0001-Make-directory-work-with-extension-control-path.patch
  • #8Apr 24, 2025
    v2-0001-Make-directory-work-with-extension-control-path.patch
  • #6Apr 23, 2025
    v1-0001-Make-directory-work-with-extension-control-path.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

This thread has been committed, so CI has stopped here. Anything below is the last result it produced.

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

Built from patchset v16 (message #16), July 27, 2026 at 09:24 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 t51265_16 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 t51265_16 && git checkout t51265_16

Patchset v16 (message #16) is on t51265_16