CI history

  • #17Jan 03, 2019Pavan Deolasee
  • #15Nov 27, 2018Pavan Deolasee
  • #11Oct 29, 2018Pavan Deolasee
  • #9Sep 24, 2018Pavan Deolasee
  • #8Sep 04, 2018Pavan Deolasee
  • #6Sep 04, 2018Pavan Deolasee
  • #1Jun 19, 2018Pavan Deolasee
  • #17Jan 03, 2019
    0001-MERGE-SQL-Command-following-SQL-2016_v7.patch
  • #15Nov 27, 2018
    0001-MERGE-SQL-Command-following-SQL-2016_v6.patch
  • #11Oct 29, 2018
    0001-MERGE-SQL-Command-following-SQL-2016_v5.patch
  • #9Sep 24, 2018
    0001-MERGE-SQL-Command-following-SQL-2016_v4.patch
  • #8Sep 04, 2018
    0001-MERGE-SQL-Command-following-SQL-2016_v3.patch
  • #7Sep 04, 2018
    crash.txt
  • #6Sep 04, 2018
    0001-MERGE-SQL-Command-following-SQL-2016_v2.patch
  • #1Jun 19, 2018
    0001-MERGE-SQL-Command-following-SQL-2016.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:t38887
psql -h localhost -U postgres

Built from patchset v17 (message #17), July 28, 2026 at 04:45 AM.

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 t38887_17 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 t38887_17 && git checkout t38887_17

Patchset v17 (message #17) is on t38887_17