CI history

  • #13Oct 12, 13:09Ayush Tiwari
  • #11Oct 12, 07:04Ayush Tiwari
  • #10Oct 02, 11:08Ayush Tiwari
  • #8Sep 18, 17:12Ayush Tiwari
  • #7Sep 12, 16:20Ayush Tiwari
  • #13Oct 12, 13:09
    v5-0001-Allow-selected-PANIC-errors-to-skip-core-dumps.patch
    v5-0003-Test-PANIC-core-dump-suppression.patch
    + 1 more
  • #11Oct 12, 07:04
    v4-0001-Allow-selected-PANIC-errors-to-skip-core-dumps.patch
    v4-0003-Test-PANIC-core-dump-suppression.patch
    + 1 more
  • #10Oct 02, 11:08
    v3-0001-Allow-selected-PANIC-errors-to-skip-core-dumps.patch
    v3-0002-Avoid-core-dumps-for-WAL-disk-full-failures.patch
  • #8Sep 18, 17:12
    v2-0002-Avoid-core-dumps-for-WAL-disk-full-failures.patch
    v2-0001-Allow-selected-PANIC-errors-to-skip-core-dumps.patch
  • #7Sep 12, 16:20
    v1-0001-Allow-selected-PANIC-errors-to-skip-core-dumps.patch
    v1-0002-Avoid-core-dumps-for-WAL-disk-full-failures.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.

needs rebasesuccessCI 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:t48753
psql -h localhost -U postgres

Built from patchset v13 (message #13), November 18, 2026 at 04:12 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 t48753_13 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 t48753_13 && git checkout t48753_13

Patchset v13 (message #13) is on t48753_13