CI history

  • #11Sep 09, 2020Amit Khandekarnew seriesLLM analysis, 98% sure
  • #6Jun 17, 2020Thomas Munrosmall revision of #5LLM analysis, 100% sure
  • #5May 14, 2020Thomas Munroreworked version of #2LLM analysis, 100% sure
  • #2Aug 24, 2019Thomas Munronew seriesLLM analysis, 100% sure
  • #11Sep 09, 2020
    guc_for_testing.patch
    0001-Avoid-redundant-tuple-copy-while-sending-tuples-to-G.patch
  • #6Jun 17, 2020
    v2-0001-Use-MinimalTuple-for-tuple-queues.patch
  • #5May 14, 2020
    0001-Use-MinimalTuple-for-tuple-queues.patch
  • #2Aug 24, 2019
    0001-Avoid-unnecessary-copying-in-tqueue.c.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 retrytests failedCI 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:t41105
psql -h localhost -U postgres

Built from patchset v11 (message #11), August 18, 2026 at 04:14 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 t41105_11 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 t41105_11 && git checkout t41105_11

Patchset v11 (message #11) is on t41105_11