CI history

  • #164 days agoMelanie Plagemanfix on top of #10LLM analysis, 100% sure
  • #10Nov 13, 22:13Melanie Plagemannew seriesLLM analysis, 100% sure
  • #3Nov 12, 22:13Melanie Plagemanrest of #2 after a partial commitLLM analysis, 100% sure
  • #2Nov 11, 23:51Melanie Plagemansmall revision of #1LLM analysis, 99% sure
  • #1Oct 21, 06:36Vaibhav Jainnew seriesLLM analysis, 100% sure
  • #164 days ago
    v1-0001-Return-NULL-for-unknown-pgstattuple-estimate.patch
  • #10Nov 13, 22:13
    v1-0001-Fix-pgstattuple_approx-handling-of-unknown-tuple-.patch
  • #3Nov 12, 22:13
    v3-0001-Exclude-new-pages-from-VACUUM-reltuples-estimates.patch
  • #2Nov 11, 23:51
    v2-0001-Avoid-unreliable-VACUUM-reltuples-estimates.patch
    v2-0002-Exclude-new-pages-from-VACUUM-reltuples-estimates.patch
  • #1Oct 21, 06:36
    0001-Fix-VACUUM-s-reltuples-estimate-when-it-skips-most-o.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.

won't retrysuccessCI history

This thread has been committed, so CI has stopped here. Anything below is the last result it produced.

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

Built from patchset v16 (message #16), November 18, 2026 at 09:48 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 t254309_16 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 t254309_16 && git checkout t254309_16

Patchset v16 (message #16) is on t254309_16