CI history

  • #20Jul 02, 20:04Pavel Stehule
  • #17Jul 02, 04:27Pavel Stehule
  • #14Jul 01, 19:51Pavel Stehule
  • #10Jun 19, 06:05Pavel Stehule
  • #6Jun 17, 07:20Pavel Stehule
  • #5Jun 16, 05:55Pavel Stehule
  • #20Jul 02, 20:04
    v20260702-6-0001-auto_explain.log_queryids.patch
  • #17Jul 02, 04:27
    v20260702-5-0001-auto_explain.log_queryids.patch
  • #14Jul 01, 19:51
    v20260701-4-0001-auto_explain.log_queryids.patch
  • #10Jun 19, 06:05
    v20260619-3-0001-auto_explain.log_queryids.patch
  • #6Jun 17, 07:20
    v20260617-2-0001-auto_explain.log_queryids.patch
  • #5Jun 16, 05:55
    v20260616-1-0001-auto_explain.log_queryids.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:t139307
psql -h localhost -U postgres

Built from patchset v20 (message #20), November 22, 2026 at 07:05 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 t139307_20 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 t139307_20 && git checkout t139307_20

Patchset v20 (message #20) is on t139307_20