CI history

  • #18Feb 28, 2025Sergey Dudoladov
  • #15May 16, 2023Sergey Dudoladov
  • #11Feb 01, 2023Sergey Dudoladov
  • #9Jan 30, 2023Sergey Dudoladov
  • #5Nov 08, 2022Sergey Dudoladov
  • #18Feb 28, 2025
    0005-Introduce-log_connection_messages.patch
  • #15May 16, 2023
    0004-Introduce-log_connection_messages.patch
  • #11Feb 01, 2023
    0003-Introduce-log_connection_messages.patch
  • #9Jan 30, 2023
    0002-Introduce-log_connection_messages.patch
  • #5Nov 08, 2022
    0001-Introduce-log_connection_messages.patch
  • #1Jul 12, 2022
    debug5_log_not_initialized_process_exit.txt

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

Built from patchset v18 (message #18), July 27, 2026 at 10:08 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 t46224_18 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 t46224_18 && git checkout t46224_18

Patchset v18 (message #18) is on t46224_18