CI history

  • #29Feb 05, 2020ideriha.takeshi@fujitsu.com
  • #23Oct 08, 2019ideriha.takeshi@fujitsu.com
  • #14Oct 03, 2018Ideriha, Takeshi
  • #1Jun 26, 2018Ideriha, Takeshi
  • #29Feb 05, 2020
    global_catalog_cache-v01.patch
    shared_memory_cotnext-v01.patch
  • #23Oct 08, 2019
    0002-POC-global-catalog-cache.patch
    0001-MemoryContext-for-shared-memory-based-on-DSA.patch
  • #14Oct 03, 2018
    0001-PoC-Allocate-catcache-on-the-shared-memory.patch
  • #1Jun 26, 2018
    001_global_meta_cache.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:t38936
psql -h localhost -U postgres

Built from patchset v29 (message #29), July 28, 2026 at 03:05 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 t38936_29 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 t38936_29 && git checkout t38936_29

Patchset v29 (message #29) is on t38936_29