Hackorum, an open source forum-style web view of the pg-hackers mailing list, has shipped a large set of new features since its February introduction. Commits are now linked back to the discussions and patches that produced them, and patch CI results (auto-apply, rebase, build, test against master) are now public with a dashboard, per-topic history, and stats overview. The tool now ingests pgsql-bugs, pgsql-docs, pgsql-general and pgsql-patches in addition to pg-hackers, with pgsql-committers imported but paused. New features include saved searches, thread ignoring, sending and replying to emails directly from the site (currently limited to Gmail accounts in testing), batch-loaded long threads, jump-to-unread, collapsible read messages, inline patch diff stats, 30-day sessions, and a revamped mobile experience. Next up is exploration of AI-generated summaries for long threads.
Table of contents
A quick recapCommits linked back to their discussionPatch CI results, now publicSupport for more mailing listsSaved searchesIgnore threads you do not care aboutSending email from HackorumEveryday improvementsMobile got a real passWhat we are working on nextTry it and share feedbackQuestions this post answers
What is Hackorum and what does it do for the PostgreSQL mailing lists?
Hackorum is an open source forum-style web view of PostgreSQL mailing lists, including pg-hackers, pgsql-bugs, pgsql-docs, pgsql-general and pgsql-patches, while the mailing list itself remains the source of truth. It syncs messages in the background, tracks read status, stars, tags and notes per user, and adds commitfest context, commit history and contributor info next to each discussion. Developers tracking PostgreSQL mailing list activity can follow tooling updates like this on daily.dev.
How does Hackorum decide when a patch is considered retired versus still active in CI?
Hackorum reapplies the latest version of each patch daily against current master and, if it stops applying, keeps retrying for 30 more days before marking it retired due to an outdated base, at which point it stops testing until a new version is posted. Once a patch is committed, CI stops running on that thread unless a new patchset follows. Contributors evaluating patch CI workflows can track tools like this on daily.dev.