CI history

  • #215Apr 15, 2019Stephen Frostfix on top of #171LLM analysis, 98% sure
  • #171Apr 03, 2019Stephen Frostsmall revision of #164LLM analysis, 100% sure
  • #164Mar 30, 2019Stephen Frostsmall revision of #162LLM analysis, 98% sure
  • #162Mar 16, 2019Stephen Frostreworked version of #145LLM analysis, 100% sure
  • #161Mar 06, 2019Robbie Harwoodfix on top of #145LLM analysis, 99% sure
  • #156Feb 21, 2019Robbie Harwoodreworked version of #146LLM analysis, 96% sure
  • #146Feb 11, 2019Stephen Frostfix on top of #145LLM analysis, 100% sure
  • #145Dec 18, 2018Robbie Harwoodsmall revision of #140LLM analysis, 100% sure
  • #140Oct 02, 2018Robbie Harwoodrebase of #130LLM analysis, 99% sure
  • #130Jun 11, 2018Robbie Harwoodsmall revision of #123LLM analysis, 100% sure
  • #123Jun 05, 2018Robbie Harwoodsmall revision of #121LLM analysis, 100% sure
  • #121May 25, 2018Robbie Harwoodsmall revision of #120LLM analysis, 100% sure
  • #120May 24, 2018Robbie Harwoodsmall revision of #116LLM analysis, 100% sure
  • #116May 23, 2018Robbie Harwoodreworked version of #87LLM analysis, 100% sure
  • #87Apr 05, 2016Robbie Harwoodsmall revision of #84LLM analysis, 100% sure
  • #84Apr 01, 2016Robbie Harwoodsmall revision of #81LLM analysis, 100% sure
  • #81Apr 01, 2016Robbie Harwoodsmall revision of #72LLM analysis, 100% sure
  • #74Mar 31, 2016Michael Paquierfix on top of #73LLM analysis, 100% sure
  • #73Mar 31, 2016Michael Paquierfix on top of #72LLM analysis, 100% sure
  • #72Mar 30, 2016Robbie Harwoodsmall revision of #66LLM analysis, 100% sure
  • #66Mar 20, 2016Robbie Harwoodsmall revision of #58LLM analysis, 100% sure
  • #58Mar 14, 2016Robbie Harwoodsmall revision of #53LLM analysis, 100% sure
  • #53Mar 08, 2016Robbie Harwoodsmall revision of #45LLM analysis, 92% sure
  • #45Feb 15, 2016Robbie Harwoodrebase of #39LLM analysis, 100% sure
  • #39Feb 10, 2016Robbie Harwoodreworked version of #18LLM analysis, 100% sure
  • #18Oct 13, 2015Robbie Harwoodsmall revision of #1LLM analysis, 97% sure
  • #6Sep 08, 2015Robbie Harwoodsmall revision of #1LLM analysis, 100% sure
  • #1Jul 02, 2015Robbie Harwoodnew seriesLLM analysis, 100% sure
  • #215Apr 15, 2019
    gssapi-doc-test-fixes_v1.patch
  • #171Apr 03, 2019
    v23-libpq-GSSAPI-encryption-support.patch
  • #164Mar 30, 2019
    v22-libpq-GSSAPI-encryption-support.patch
  • #162Mar 16, 2019
    v21-libpq-GSSAPI-encryption-support.patch
  • #161Mar 06, 2019
    Add-tests-for-GSSAPI-krb5-encryption.patch
  • #156Feb 21, 2019
    Log-encryption-strength-in-libpq-GSSAPI-connections.patch
  • #146Feb 11, 2019
    print-gssapi-sasl-ssf-psql.patch
  • #145Dec 18, 2018
    v20-libpq-GSSAPI-encryption-support.patch
  • #140Oct 02, 2018
    v19-libpq-GSSAPI-encryption-support.patch
  • #130Jun 11, 2018
    v18-libpq-GSSAPI-encryption-support.patch
  • #123Jun 05, 2018
    v17-libpq-GSSAPI-encryption-support.patch
  • #121May 25, 2018
    v16-libpq-GSSAPI-encryption-support.patch
  • #120May 24, 2018
    v15-libpq-GSSAPI-encryption-support.patch
  • #116May 23, 2018
    v14-libpq-GSSAPI-encryption-support.patch
  • #87Apr 05, 2016
    v12-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    v12-0002-Connection-encryption-support-for-GSSAPI.patch
    + 1 more
  • #84Apr 01, 2016
    v11-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    v11-0002-Connection-encryption-support-for-GSSAPI.patch
    + 1 more
  • #81Apr 01, 2016
    v10-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    v10-0002-Connection-encryption-support-for-GSSAPI.patch
    + 1 more
  • #74Mar 31, 2016
    gssapi-enc-fix-msvc-2.patch
  • #73Mar 31, 2016
    gssapi-enc-fix-msvc.patch
  • #72Mar 30, 2016
    v9-0002-Connection-encryption-support-for-GSSAPI.patch
    v9-0003-GSSAPI-authentication-cleanup.patch
    + 1 more
  • #66Mar 20, 2016
    v8-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    v8-0002-Connection-encryption-support-for-GSSAPI.patch
    + 1 more
  • #58Mar 14, 2016
    v7-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    v7-0002-Connection-encryption-support-for-GSSAPI.patch
    + 1 more
  • #54Mar 09, 2016
    gssapi.pcap
  • #53Mar 08, 2016
    v6-0003-GSSAPI-authentication-cleanup.patch
    v6-0001-Move-common-GSSAPI-code-into-its-own-files.patch
    + 1 more
  • #45Feb 15, 2016
    v5-GSSAPI-encryption-support.patch
  • #44Feb 12, 2016
    gssauth-fail.log
    gssauth-success.log
  • #39Feb 10, 2016
    v4-GSSAPI-encryption-support.patch
  • #18Oct 13, 2015
    v3-GSSAPI-encryption-support.patch
  • #6Sep 08, 2015
    v2-8-Document-GSSAPI-encryption.patch
  • #1Jul 02, 2015
    v1-1-build-Define-with_gssapi-for-use-in-Makefiles.patch
    v1-2-client-Disable-GSS-encryption-on-old-servers.patch
    + 6 more

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

Built from patchset v215 (message #215), August 18, 2026 at 04:41 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 t33105_215 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 t33105_215 && git checkout t33105_215

Patchset v215 (message #215) is on t33105_215