CI history

  • #236 days agoDavid Geier
  • #21Oct 23, 08:18David Geier
  • #17Sep 17, 08:13David Geier
  • #11Mar 02, 13:47David Geier
  • #10Mar 02, 12:04David Geier
  • #9Feb 03, 11:03David Geier
  • #7Jan 30, 08:42David Geier
  • #4Jan 23, 15:10David Geier
  • #1Jan 21, 15:36David Geier
  • #236 days ago
    v9-0001-Use-correct-collation-for-lowercasing.patch
    v9-0002-Use-correct-collation-for-finding-word-boundaries.patch
  • #21Oct 23, 08:18
    v8-0001-Use-correct-collation-for-lowercasing.patch
    v8-0002-Use-correct-collation-for-finding-word-boundaries.patch
  • #17Sep 17, 08:13
    v7-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v7-0001-Use-correct-collation-for-lowercasing.patch
  • #11Mar 02, 13:47
    v6-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v6-0001-Use-correct-collation-for-lowercasing.patch
  • #10Mar 02, 12:04
    v5-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v5-0001-Use-correct-collation-for-lowercasing.patch
  • #9Feb 03, 11:03
    v4-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v4-0001-Use-correct-collation-for-lowercasing.patch
  • #7Jan 30, 08:42
    v3-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v3-0001-Use-correct-collation-for-lowercasing.patch
  • #4Jan 23, 15:10
    v2-0002-Use-correct-collation-for-finding-word-boundaries.patch
    v2-0001-Use-correct-collation-for-lowercasing.patch
  • #1Jan 21, 15:36
    v1-0001-Use-correct-collation-in-pg_trgm.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:t53142
psql -h localhost -U postgres

Built from patchset v23 (message #23), November 21, 2026 at 04: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 t53142_23 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 t53142_23 && git checkout t53142_23

Patchset v23 (message #23) is on t53142_23