CI history

  • #149May 15, 2024Bruce Momjiannew seriesLLM analysis, 100% sure
  • #142May 12, 2024Alvaro Herreranew seriesLLM analysis, 100% sure
  • #139May 08, 2024Alvaro Herreranew seriesLLM analysis, 99% sure
  • #134May 01, 2024Alvaro Herrerasmall revision of #131LLM analysis, 99% sure
  • #131Apr 24, 2024Alvaro Herrerasmall revision of #130LLM analysis, 100% sure
  • #130Apr 22, 2024Alvaro Herreranew seriesLLM analysis, 100% sure
  • #125Feb 05, 2024Alvaro Herrerasmall revision of #122LLM analysis, 100% sure
  • #122Feb 05, 2024Alvaro Herreranew seriesLLM analysis, 100% sure
  • #110Aug 31, 2023Alvaro Herreranew seriesLLM analysis, 100% sure
  • #103Aug 23, 2023Alvaro Herrerasmall revision of #102LLM analysis, 98% sure
  • #102Aug 21, 2023Alvaro Herrerareworked version of #97LLM analysis, 96% sure
  • #97Aug 11, 2023Alvaro Herrerasmall revision of #78LLM analysis, 94% sure
  • #78Jul 25, 2023Alvaro Herrerasmall revision of #74LLM analysis, 99% sure
  • #74Jul 24, 2023Alvaro Herrerasmall revision of #66LLM analysis, 100% sure
  • #66Jul 20, 2023Alvaro Herrerasmall revision of #64LLM analysis, 100% sure
  • #64Jul 12, 2023Alvaro Herrerarebase of #63LLM analysis, 98% sure
  • #63Jul 11, 2023Alvaro Herrerasmall revision of #62LLM analysis, 100% sure
  • #62Jul 11, 2023Alvaro Herrerasmall revision of #61LLM analysis, 100% sure
  • #61Jul 10, 2023Alvaro Herrerasmall revision of #57LLM analysis, 99% sure
  • #57Jun 30, 2023Alvaro Herrerareworked version of #40LLM analysis, 98% sure
  • #40Apr 07, 2023Alvaro Herrerasmall revision of #39LLM analysis, 100% sure
  • #39Apr 07, 2023Alvaro Herrerasmall revision of #35LLM analysis, 99% sure
  • #35Apr 05, 2023Alvaro Herrerasmall revision of #32LLM analysis, 98% sure
  • #32Mar 15, 2023Alvaro Herrerasmall revision of #28LLM analysis, 94% sure
  • #28Mar 01, 2023Alvaro Herrerasmall revision of #27LLM analysis, 100% sure
  • #27Feb 28, 2023Alvaro Herrerareworked version of #12LLM analysis, 100% sure
  • #12Sep 09, 2022Alvaro Herrerasmall revision of #9LLM analysis, 96% sure
  • #9Aug 31, 2022Alvaro Herreranew seriesLLM analysis, 100% sure
  • #149May 15, 2024
    master.diff
  • #142May 12, 2024
    revert-not-null.patch
  • #139May 08, 2024
    0003-pgindent-run.patch
    0004-Take-PQfnumber-calls-out-of-the-routine.patch
    + 4 more
  • #134May 01, 2024
    0001-Disallow-direct-change-of-NO-INHERIT-of-not-null-con.patch
    0002-Disallow-NO-INHERIT-not-null-constraints-on-partitio.patch
  • #131Apr 24, 2024
    v2-0001-Acquire-locks-on-children-before-recursing.patch
    v2-0002-Disallow-changing-NO-INHERIT-property-of-a-constr.patch
  • #130Apr 22, 2024
    0001-Acquire-locks-on-children-before-recursing.patch
  • #125Feb 05, 2024
    v2-0001-Fix-failure-to-merge-NOT-NULL-constraints-in-inhe.patch
    v2-0002-ATTACH-PARTITION-Don-t-let-a-UNIQUE-constraint-ma.patch
  • #122Feb 05, 2024
    v1-0001-Fix-failure-to-merge-NOT-NULL-constraints-in-inhe.patch
  • #110Aug 31, 2023
    0001-Fix-not-null-constraint-test.patch
  • #103Aug 23, 2023
    v19-0001-Catalog-NOT-NULL-constraints.patch
  • #102Aug 21, 2023
    v18-0001-Catalog-NOT-NULL-constraints.patch
  • #101Aug 16, 2023
    0001-fixup-Have-psql-print-the-NOT-NULL-constraints-on-d.patch.nocfbot
    0002-Update-ddl.sgml-for-named-not-null-constraints.patch.nocfbot
  • #97Aug 11, 2023
    v17-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch
    v17-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
    + 1 more
  • #78Jul 25, 2023
    v16-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch
    v16-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
    + 1 more
  • #74Jul 24, 2023
    v15-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch
    v15-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #66Jul 20, 2023
    v14-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch
    v14-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #64Jul 12, 2023
    v13-0001-Remember-PK-oid-for-partitioned-tables-even-when.patch
    v13-0002-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #63Jul 11, 2023
    v12-0001-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #62Jul 11, 2023
    v11-0001-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #61Jul 10, 2023
    v10-0001-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #60Jul 03, 2023
    0001-fixup-Add-pg_constraint-rows-for-NOT-NULL-constraint.patch.nocfbot
  • #57Jun 30, 2023
    v9-0001-Add-pg_constraint-rows-for-NOT-NULL-constraints.patch
  • #40Apr 07, 2023
    v8-0001-Catalog-NOT-NULL-constraints.patch
  • #39Apr 07, 2023
    v7-0001-Catalog-NOT-NULL-constraints.patch
  • #35Apr 05, 2023
    v6-0001-Catalog-NOT-NULL-constraints.patch
  • #34Mar 29, 2023
    0001-Add-tests-for-information-schema-constraints.patch.nocfbot
    0002-Update-information-schema-for-catalogued-not.patch.nocfbot
  • #32Mar 15, 2023
    v5-0001-Catalog-NOT-NULL-constraints.patch
  • #28Mar 01, 2023
    v4-0001-ALTER-TABLE-ADD-PRIMARY-KEY-mention-table-name-in.patch
    v4-0002-Rebase-of-catalog-notnull-6-minus-psql-d-changes.patch
    + 1 more
  • #27Feb 28, 2023
    v3-0001-ALTER-TABLE-ADD-PRIMARY-KEY-mention-table-name-in.patch
    v3-0002-Rebase-of-catalog-notnull-6-minus-psql-d-changes.patch
    + 1 more
  • #12Sep 09, 2022
    notnull-constraints-2.patch
  • #9Aug 31, 2022
    notnull-constraints-1.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

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

Built from patchset v149 (message #149), August 18, 2026 at 03:04 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 t46431_149 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 t46431_149 && git checkout t46431_149

Patchset v149 (message #149) is on t46431_149