gitzette / @levkk / Mar 2 – Mar 8 W10
← W09 W10 W11 →
@levkk — open-source digest February 23 – March 1, 2026
Vol. 1, No. -1 github.com/levkk
the dispatch
@levkk
Online resharding lands, replicas get put on probation, and Postgres remains enough.
6 commits 6 PRs 1 release 4 repos

One Helm release, two heavyweight PRs, and a philosophical declaration about database sufficiency.

RELEASE

helm v0.45 ships with a fix nobody asked @levkk for

A community contributor upgrades the ExternalSecret API version, and the Helm chart gets a fresh tag.

helm v0.45 landed on February 25 with a single but meaningful change: switching to the v1 ExternalSecret apiVersion. The patch came from first-time contributor @mikkelam. Not every release needs fireworks. Sometimes the plumbing just needs a new fitting.

FEATURE

pgdog learns to reshard a live database without pulling the plug

Online resharding arrives in pgdog, letting operators rebalance data across shards without downtime.

The headliner this week is #784 Online resharding, merged by @levkk. This gives pgdog the ability to move data between shards while the system stays up and serving queries. Accompanying documentation also shipped: #55 feat: document new reshard command and schema sync and #56 Document cutover landed in docs the same week. The feature arrived with its own manual. Rare courtesy.

FEATURE

Slow replicas now get benched automatically

Replica lag banning plus a batch of bug fixes traced back to Hacker News feedback.

@levkk merged #788 replica lag banning, multiple bug fixes from HN, which introduces automatic banning of replicas that fall behind on replication. The PR also bundles several bug fixes surfaced by the Hacker News crowd. Nothing like a front-page post to shake loose the edge cases.

the dispatch — Vol. 1, No. -1 February 23 – March 1, 2026
FEATURE

docs catches up to the resharding train

Two PRs document cutover procedures and the new reshard command before users have to guess.

@levkk merged #55 feat: document new reshard command and schema sync and #56 Document cutover in the docs repo. The reshard command, schema sync behavior, and cutover procedures all got written up. Five open issues remain on the backlog, including one to generate an LLM-friendly text dump at /llms.txt. The machines want docs too, apparently.

PENDING

Wildcard database templates waiting at the door

A community PR proposes letting pgdog match databases by pattern instead of explicit config.

Contributor @hikionori has #794 feat: add wildcard database template support open against pgdog. If merged, operators could define database connection templates using wildcards rather than listing every database individually. The PR is still under review.

COMMUNITY

pgdog joins the "Postgres is enough" registry

@levkk adds pgdog to the curated list of tools that bet everything on Postgres.

@levkk merged #2 feat: add PgDog into postgresisenough, the community-maintained catalog of projects built on the conviction that Postgres handles more than you think. One open issue notes the auth tag is misbehaving. Philosophical certainty, minor technical uncertainty.

stats corner
6
commits
6
pull requests
1
releases
commits by repo
REPO COMMITS docs 2 pgdog 2 helm 1 postgresisenough 1
github stars
pgdog
4,202
helm
11
postgresisenough
11
docs
4
release timeline
MONTUEWEDTHUFRISATSUN helm v0.45
repo index
  • docs
    PgDog documentation.
    2 commits · 0 releases · ★ 4
  • helm
    Helm chart for deploying PgDog.
    1 commits · 1 release · ★ 11
  • pgdog
    PostgreSQL connection pooler, load balancer and database sharder.
    2 commits · 0 releases · ★ 4202
  • postgresisenough
    Postgres Is Enough
    1 commits · 0 releases · ★ 11
Mar 9 – Mar 15 →
gitzette @levkk on gitzette @levkk on GitHub
share: post on X share on LinkedIn

Your GitHub week, turned into something worth reading.

Generate your dispatch →
gitzette.online  ·  2026 © AISlopMedia, Inc.