CI history

  • #8Jun 17, 2025Yan Haibo
  • #6Jun 16, 2025Yan Haibo
  • #4Jun 16, 2025Yan Haibo
  • #3Jun 16, 2025Yan Haibo
  • #1Jun 06, 2025Yan Haibo
  • #8Jun 17, 2025
    0001-Mitigate-potential-overflow-risks-from-wcscpy.patch
  • #6Jun 16, 2025
    0001-Mitigate-potential-overflow-risks-from-wcscpy.patch
  • #4Jun 16, 2025
    0001-Mitigate-potential-overflow-risks-from-wcscpy-and-sp.patch
  • #3Jun 16, 2025
    0001-Mitigate-potential-overflow-risks-from-wcscpy-and-sp.patch
  • #1Jun 06, 2025
    0001-Mitigate-potential-overflow-risks-from-wcscpy-and-sp.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.

appliessuccessCI 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:t51707
psql -h localhost -U postgres

Built from patchset v8 (message #8), November 22, 2026 at 03:02 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 t51707_8 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 t51707_8 && git checkout t51707_8

Patchset v8 (message #8) is on t51707_8