CI history

  • #65Mar 18, 2025Jelte Fennema-Niorest of #61 after a partial commitLLM analysis, 100% sure
  • #61Feb 18, 2025Jelte Fennema-Niorebase of #60LLM analysis, 100% sure
  • #60Jun 27, 2024Jelte Fennema-Niosmall revision of #27LLM analysis, 98% sure
  • #32Apr 18, 2024Michael Paquierreworked version of #27LLM analysis, 88% sure
  • #27Mar 22, 2024Jelte Fennema-Niosmall revision of #26LLM analysis, 100% sure
  • #26Mar 21, 2024Jelte Fennema-Nioreworked version of #22LLM analysis, 100% sure
  • #22Mar 11, 2024Jelte Fennema-Niosmall revision of #19LLM analysis, 100% sure
  • #19Mar 08, 2024Jelte Fennema-Niosmall revision of #14LLM analysis, 100% sure
  • #14Mar 08, 2024Jelte Fennema-Niosmall revision of #7LLM analysis, 99% sure
  • #12Mar 08, 2024Bharath Rupireddyreworked version of #7LLM analysis, 96% sure
  • #7Feb 28, 2024Jelte Fennema-Niosmall revision of #5LLM analysis, 100% sure
  • #5Feb 27, 2024Jelte Fennema-Niosmall revision of #2LLM analysis, 94% sure
  • #2Feb 12, 2024Daniel Gustafssonsmall revision of #1LLM analysis, 100% sure
  • #1Dec 20, 2023Jelte Fennema-Nionew seriesLLM analysis, 100% sure
  • #65Mar 18, 2025
    v12-0001-Allow-logging-backtraces-in-more-cases.patch
  • #61Feb 18, 2025
    v11-0002-Allow-logging-backtraces-in-more-cases.patch
    v11-0001-Add-PGErrorVerbosity-to-typedefs.list.patch
  • #60Jun 27, 2024
    0001-Add-PGErrorVerbosity-to-typedefs.list.patch
    0002-Allow-logging-backtraces-in-more-cases.patch
  • #32Apr 18, 2024
    0001-backtrace_on_internal_error-backtrace_mode.patch
  • #27Mar 22, 2024
    v9-0003-Change-log_backtrace-default-to-internal.patch
    v9-0002-Restructure-backtrace-related-GUCs.patch
    + 1 more
  • #26Mar 21, 2024
    v8-0001-Add-PGErrorVerbosity-to-typedefs.list.patch
    v8-0002-Restructure-backtrace-related-GUCs.patch
  • #22Mar 11, 2024
    v7-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
    v7-0001-Add-backtrace_functions_min_level.patch
  • #19Mar 08, 2024
    v6-0001-Add-backtrace_functions_min_level.patch
    v6-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
  • #14Mar 08, 2024
    v5-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
    v5-0001-Add-backtrace_functions_min_level.patch
  • #12Mar 08, 2024
    v4-0001-Add-backtrace_functions_min_level.patch
    v4-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
    + 1 more
  • #7Feb 28, 2024
    v4-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
    v4-0001-Add-backtrace_functions_min_level.patch
  • #5Feb 27, 2024
    v3-0002-Add-wildcard-support-to-backtrace_functions-GUC.patch
    v3-0001-Add-backtrace_functions_min_level.patch
  • #2Feb 12, 2024
    v2-0002-Support-wildcard-in-backtrace_functions-to-handle.patch
    v2-0001-doc-Clarify-when-backtrace_functions-is-invoked.patch
  • #1Dec 20, 2023
    v1-0001-Add-wildcard-support-to-backtrace_functions-GUC.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:t48922
psql -h localhost -U postgres

Built from patchset v65 (message #65), August 18, 2026 at 02:44 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 t48922_65 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 t48922_65 && git checkout t48922_65

Patchset v65 (message #65) is on t48922_65