CI history

  • #29Mar 31, 2017Alexander Korotkov
  • #26Mar 25, 2017Alexander Korotkov
  • #5Feb 06, 2017Alexander Korotkov
  • #1Feb 03, 2017Alexander Korotkov
  • #29Mar 31, 2017
    lwlock-power-5.patch
  • #26Mar 25, 2017
    lwlock-power-4.patch
  • #21Feb 21, 2017
    wait_sampling_profile_writes.txt
  • #19Feb 21, 2017
    pgbench-ro.png
    pgbench-reads-writes.png
    + 5 more
  • #10Feb 07, 2017
    bench.png
    lwlocks-power-1-results.txt
    + 2 more
  • #5Feb 06, 2017
    lwlock-power-3.patch
  • #1Feb 03, 2017
    power8-lwlock-asm-ro.png
    lwlock-power-1.patch
    + 1 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.

never appliedsuccessCI 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:t35964
psql -h localhost -U postgres

Built from patchset v29 (message #29), July 28, 2026 at 02:27 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 t35964_29 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 t35964_29 && git checkout t35964_29

Patchset v29 (message #29) is on t35964_29