CI history

  • #43Aug 19, 2022David Zhangnew seriesLLM analysis, 98% sure
  • #32Aug 01, 2022Ranier Vilelarest of #29 after a partial commitLLM analysis, 99% sure
  • #29Jul 11, 2022Ranier Vilelarebase of #27LLM analysis, 98% sure
  • #27Jul 07, 2022Ranier Vilelasmall revision of #22LLM analysis, 99% sure
  • #22Jul 07, 2022Peter Eisentrautreworked version of #17LLM analysis, 94% sure
  • #21Jul 01, 2022Ranier Vilelarest of #17 after a partial commitLLM analysis, 98% sure
  • #17May 19, 2022Ranier Vilelareworked version of #4LLM analysis, 99% sure
  • #4May 17, 2022Ranier Vilelareworked version of #1LLM analysis, 94% sure
  • #1May 14, 2022Ranier Vilelanew seriesLLM analysis, 100% sure
  • #43Aug 19, 2022
    0001-Replace-many-memset-calls-with-struct-initialization.patch
  • #32Aug 01, 2022
    v3-0001-WIP-Replace-MemSet-calls-with-struct-initialization.patch
  • #29Jul 11, 2022
    v2-0001-WIP-Replace-MemSet-calls-with-struct-initialization.patch
  • #27Jul 07, 2022
    v1-0001-WIP-Replace-MemSet-calls-with-struct-initialization.patch
  • #22Jul 07, 2022
    0001-WIP-Replace-MemSet-calls-with-struct-initialization.patch
  • #21Jul 01, 2022
    001-avoid-unecessary-MemSet-calls.patch
  • #17May 19, 2022
    001_avoid_unecessary_memset_call.patch
    002_refactoring_memset_api_usage.patch
  • #12May 18, 2022
    memset.c
  • #4May 17, 2022
    001-avoid_unecessary_memset_call.patch
    002-fix_api_memset_usage.patch
  • #1May 14, 2022
    avoid_unecessary_memset_call.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:t45950
psql -h localhost -U postgres

Built from patchset v43 (message #43), August 18, 2026 at 03:47 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 t45950_43 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 t45950_43 && git checkout t45950_43

Patchset v43 (message #43) is on t45950_43