CI history

  • #454 days agoAlberto Piaismall revision of #42LLM analysis, 100% sure
  • #42Nov 06, 12:36Alberto Piaireworked version of #29LLM analysis, 97% sure
  • #29Sep 16, 17:02Alberto Piaismall revision of #25LLM analysis, 98% sure
  • #25Aug 31, 18:41Alberto Piaismall revision of #21LLM analysis, 99% sure
  • #21Aug 28, 05:50Alberto Piaismall revision of #17LLM analysis, 98% sure
  • #17Aug 24, 20:03Alberto Piaismall revision of #15LLM analysis, 100% sure
  • #15Aug 06, 12:36Alberto Piaismall revision of #11LLM analysis, 99% sure
  • #11Jul 03, 06:42Alberto Piaismall revision of #10LLM analysis, 100% sure
  • #10Jun 30, 13:44Alberto Piaireworked version of #4LLM analysis, 100% sure
  • #4May 14, 22:46Alberto Piaismall revision of #3LLM analysis, 99% sure
  • #3Apr 24, 09:10Alberto Piairebase of #2LLM analysis, 99% sure
  • #2Apr 07, 09:09Alberto Piaismall revision of #1LLM analysis, 99% sure
  • #1Mar 17, 10:31Alberto Piainew seriesLLM analysis, 100% sure
  • #454 days ago
    v13-0001-Add-SQL-level-datum-equality-tests.patch
    v13-0002-Support-changing-a-column-into-a-stored-generate.patch
  • #42Nov 06, 12:36
    v12-0001-Add-SQL-level-datum-equality-tests.patch
    v12-0002-Support-changing-a-column-into-a-stored-generate.patch
  • #29Sep 16, 17:02
    v11-0001-Support-changing-a-column-into-a-stored-generate.patch
  • #25Aug 31, 18:41
    v10-0001-Support-changing-a-column-into-a-stored-generate.patch
  • #21Aug 28, 05:50
    v9-0001-Support-changing-a-column-into-a-stored-generated.patch
  • #17Aug 24, 20:03
    v8-0001-Support-changing-a-column-into-a-stored-generated.patch
  • #15Aug 06, 12:36
    v7-0001-Support-changing-a-column-into-a-stored-generated.patch
  • #11Jul 03, 06:42
    v6-0001-Support-changing-a-column-into-a-stored-generated.patch
  • #10Jun 30, 13:44
    v5-0001-Support-changing-a-column-into-a-stored-generated.patch
    039_stored_generated_published.pl
    + 1 more
  • #4May 14, 22:46
    v4-0001-Support-changing-a-column-into-a-stored-generated.patch
    v4-0002-Try-to-avoid-a-rewrite-when-adding-a-stored-gener.patch
  • #3Apr 24, 09:10
    v3-0001-Support-changing-a-column-into-a-stored-generated.patch
    v3-0002-Try-to-avoid-a-rewrite-when-adding-a-stored-gener.patch
  • #2Apr 07, 09:09
    v2-0001-Support-changing-a-column-into-a-stored-generated.patch
    v2-0002-Try-to-avoid-a-rewrite-when-adding-a-stored-gener.patch
  • #1Mar 17, 10:31
    v1-0001-Support-changing-a-column-into-a-stored-generated.patch
    v1-0002-Try-to-avoid-a-rewrite-when-adding-a-stored-gener.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:t53518
psql -h localhost -U postgres

Built from patchset v45 (message #45), November 22, 2026 at 04:58 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 t53518_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 t53518_45 && git checkout t53518_45

Patchset v45 (message #45) is on t53518_45