CI history

  • #45Oct 08, 2021David Fettersmall revision of #44LLM analysis, 97% sure
  • #44Sep 22, 2018Edmund Hornerrebase of #42LLM analysis, 98% sure
  • #42Jul 17, 2018Edmund Hornersmall revision of #34LLM analysis, 93% sure
  • #34Mar 08, 2018Edmund Hornersmall revision of #33LLM analysis, 100% sure
  • #33Mar 06, 2018Edmund Hornerreworked version of #19LLM analysis, 100% sure
  • #23Mar 04, 2018Tom Lanenew seriesLLM analysis, 99% sure
  • #19Jan 26, 2018Edmund Hornersmall revision of #8LLM analysis, 100% sure
  • #9Jan 15, 2018Edmund Hornernew seriesLLM analysis, 95% sure
  • #8Jan 12, 2018Edmund Hornersmall revision of #1LLM analysis, 100% sure
  • #1Nov 06, 2017Edmund Hornernew seriesLLM analysis, 100% sure
  • #45Oct 08, 2021
    v9-0001-Infrastructure-for-tab-completion-in-the-SELECT-l.patch
    v9-0002-SELECT-completion-after-commas.patch
  • #44Sep 22, 2018
    01-psql-select-tab-completion-v8.patch
    02-select-completion-after-commas.patch
  • #42Jul 17, 2018
    psql-select-tab-completion-v7.patch
    select-comma-completion-v1.patch
  • #34Mar 08, 2018
    psql-select-tab-completion-v6.patch
  • #33Mar 06, 2018
    psql-select-tab-completion-v5.patch
  • #23Mar 04, 2018
    version-dependent-tab-completion-1.patch
  • #19Jan 26, 2018
    psql-select-tab-completion-v3.patch
  • #9Jan 15, 2018
    psql-tab-completion-savepoint-v1.patch
  • #8Jan 12, 2018
    psql-select-tab-completion-v2.patch
  • #1Nov 06, 2017
    psql-select-tab-completion-v1.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:t37679
psql -h localhost -U postgres

Built from patchset v45 (message #45), August 18, 2026 at 03:57 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 t37679_45 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 t37679_45 && git checkout t37679_45

Patchset v45 (message #45) is on t37679_45