CI history

  • #30Mar 09, 2019Magnus Hagander
  • #27Feb 06, 2019Timmer, Marius
  • #23Nov 30, 2018Timmer, Marius
  • #20Oct 25, 2018Timmer, Marius
  • #18Aug 03, 2018David Fetter
  • #15Jul 14, 2018Julian Markwort
  • #13Apr 13, 2018Julian Markwort
  • #9Apr 06, 2018Magnus Hagander
  • #5Mar 23, 2018Julian Markwort
  • #1Feb 16, 2018Julian Markwort
  • #30Mar 09, 2019
    clientcert_verify_full_v07_4.patch
  • #27Feb 06, 2019
    clientcert_verify_full_v07_3.patch
  • #23Nov 30, 2018
    clientcert_verify_full_v07_2.patch
    smime.p7s
  • #21Oct 25, 2018
    smime.p7s
  • #20Oct 25, 2018
    clientcert_verify_full_v07.patch
    smime.p7s
  • #18Aug 03, 2018
    0001-clientcert_verify_full-v06.patch
  • #15Jul 14, 2018
    clientcert_verify_full_v05.patch
  • #13Apr 13, 2018
    clientcert_verify_full_v04.patch
  • #9Apr 06, 2018
    clientcert_verify_full_v03.patch
  • #5Mar 23, 2018
    clientcert_verify_full_v02.patch
  • #1Feb 16, 2018
    clientcert_verify-full_v01.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:t38203
psql -h localhost -U postgres

Built from patchset v30 (message #30), July 28, 2026 at 04:34 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 t38203_30 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 t38203_30 && git checkout t38203_30

Patchset v30 (message #30) is on t38203_30