CI history

  • #24Dec 03, 2021Dinesh Chemuduru
  • #20Nov 08, 2021Dinesh Chemuduru
  • #15Nov 07, 2021Dinesh Chemuduru
  • #13Nov 05, 2021Dinesh Chemuduru
  • #5Aug 20, 2021Dinesh Chemuduru
  • #1Jul 16, 2021Dinesh Chemuduru
  • #24Dec 03, 2021
    05_diag_parse_sql_statement.patch
  • #20Nov 08, 2021
    05_diag_parse_sql_statement.patch
  • #15Nov 07, 2021
    04_diag_parse_sql_statement.patch
  • #13Nov 05, 2021
    03_diag_parse_sql_statement.patch
  • #5Aug 20, 2021
    02_diag_parse_sql_statement.patch
  • #1Jul 16, 2021
    01_diag_parse_sql_statement.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:t44570
psql -h localhost -U postgres

Built from patchset v24 (message #24), July 27, 2026 at 03:51 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 t44570_24 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 t44570_24 && git checkout t44570_24

Patchset v24 (message #24) is on t44570_24