CI history

  • #36 minutes agoNarek Galstyan
  • #2about 3 hours agoHeikki Linnakangas
  • #12 days agoNarek Galstyan
  • #36 minutes ago
    0002-Document-that-generic-WAL-logs-init-fork-pages.patch
    0001-Flush-init-fork-pages-after-generic-WAL-delta-redo.patch
  • #2about 3 hours ago
    0001-Fix-WAL-logging-init-fork-for-unlogged-rels-with-gen.patch
  • #12 days ago
    0002-Fix-init-fork-unlogged-table-WAL-logging-of-bloom-in.patch
    0001-Add-tests-for-crash-recovery-with-unlogged-bloom-ind.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.

awaiting CIrunningCI 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:t254533
psql -h localhost -U postgres

This image is from patchset v2 (message #2) - the current patchset v3 (message #3) has not produced an image.

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 t254533_3 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 t254533_3 && git checkout t254533_3

Patchset v3 (message #3) is on t254533_3