CI history

  • #7Jan 22, 2019Pavel Stehulesmall revision of #5LLM analysis, 100% sure
  • #5Jan 18, 2019Pavel Stehulesmall revision of #3LLM analysis, 100% sure
  • #3Jan 04, 2019Pavel Stehulesmall revision of #1LLM analysis, 100% sure
  • #1Nov 13, 2018Pavel Stehulenew seriesLLM analysis, 100% sure
  • #7Jan 22, 2019
    plpgsql-statement-id-04.patch
  • #5Jan 18, 2019
    plpgsql-statement-id-03.patch
  • #3Jan 04, 2019
    plpgsql-statement-id-02.patch
  • #1Nov 13, 2018
    plpgsql-statement-id.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:t39666
psql -h localhost -U postgres

Built from patchset v7 (message #7), July 28, 2026 at 04:44 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 t39666_7 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 t39666_7 && git checkout t39666_7

Patchset v7 (message #7) is on t39666_7