gitzette / @NikolayS / Apr 6 – Apr 12 W15
← W14 W15 W16 →
gitzette.online — open-source digest Apr 6 – Apr 13, 2026
the dispatch
@NikolayS
psql compatibility: the thousand paper cuts nobody warned you about
14 commits 8 PRs merged 0 releases 9 repos Eight PRs just to match psql's output formatting. One of them was a revert of the one before it.
FEATURE

rpg learns that psql's output format is a dialect, not a standard

Eight PRs this week just to match how psql wraps text, reports errors, and formats partitions.

rpg

Passing psql's regression tests means matching behavior nobody documented — including ASCII-wrapped column edge cases (#809) and the exact error location prefix format (#803). @NikolayS landed a combined alignment and describe fix in #788, but only after reverting a previous attempt in #786. Even the test harness needed work: bash 3.2 compatibility (#801) and WAL timing variance normalization (#802) because CI doesn't care about your feelings. The partition relation titles alone needed a PG14-17 normalization pass (#800).

PENDING

copy_in was sending Sync twice — and Postgres was listening both times

Three upstream PRs pending: a protocol crash, a missing OID accessor, and a stray import.

The tokio-postgres copy_in implementation could fire a double-Sync, which Postgres interprets as two transaction boundaries — not ideal when you meant one. @NikolayS's #1337 fixes the protocol state machine. Also pending: exposing type OIDs on SimpleColumn (#1338) so callers can actually inspect what they're getting, and guarding a PathBuf import that only makes sense on Unix (#1336).

PENDING

pgdog kept expecting ReadyForQuery while Postgres was already in COPY mode

A pending fix for a protocol state mismatch that left connections hung.

When a server enters COPY IN mode, it stops sending ReadyForQuery — but pgdog's connection state didn't get the memo, leaving it waiting for a message that would never arrive. @NikolayS's #885 drops the stale expectation so the pooler can actually forward the COPY stream.

COMMUNITY

three commits to the fork, zero PRs surfaced

Activity on the local rust-postgres fork without merged PRs to show for it.

Three commits landed in @NikolayS's rust-postgres fork this week. The upstream PRs (#1337, #1338, #1336) are still pending review — the fork is where the work happens before it goes anywhere.

FEATURE

gitzette gets a single commit, contents unknown

The newspaper generator saw some activity, but no PRs to dissect.

gitzette

One commit to the repo that turns GitHub activity into weekly newspapers. What changed? The commit data doesn't say, and neither will we.

FEATURE

dispatch infrastructure: one commit, no elaboration

The generator's output repo saw minor activity.

gitzette-dispatch

A single commit landed in gitzette-dispatch, the repo that actually produces these weekly editions. Presumably it helped. No PR to cite.

FEATURE

spqr: one commit, no details

The stateless query router saw a lone commit this week.

spqr

One commit to spqr with no associated PR data. The query router remains stateless; so does this write-up.

COMMUNITY

database-lab-engine: quiet week

No commits, no PRs, no releases.

DBLab took the week off. Thin clones remain thin. Branches remain branchable.

COMMUNITY

postgres-ai/docs: nothing to report

The docs stayed exactly as they were.

Zero commits to the PostgresAI documentation. Either everything was already perfectly explained, or nobody tried to explain anything new.

14
commits
12
pull requests
0
releases
commits by repo
REPO COMMITS rpg 8rust-postgres 3gitzette 1gitzette-dispatch 1spqr 1
github stars
pgdogdev/pgdog ★★★★★★★★★★ 4,279
rust-postgres/rust-postgres ★★★★★★★★★ 3,925
postgres-ai/database-lab-engine ★★★★★★☆☆☆☆ 2,444
rpg ☆☆☆☆☆☆☆☆☆ 222
gitzette ☆☆☆☆☆☆☆☆☆ 4
gitzette-dispatch ☆☆☆☆☆☆☆☆☆ 1
continued2026-W15
the dispatch
FEATURE

dispatch infrastructure: one commit, no elaboration

The generator's output repo saw minor activity.

gitzette-dispatch

A single commit landed in gitzette-dispatch, the repo that actually produces these weekly editions. Presumably it helped. No PR to cite.

FEATURE

spqr: one commit, no details

The stateless query router saw a lone commit this week.

spqr

One commit to spqr with no associated PR data. The query router remains stateless; so does this write-up.

COMMUNITY

database-lab-engine: quiet week

No commits, no PRs, no releases.

DBLab took the week off. Thin clones remain thin. Branches remain branchable.

COMMUNITY

postgres-ai/docs: nothing to report

The docs stayed exactly as they were.

Zero commits to the PostgresAI documentation. Either everything was already perfectly explained, or nobody tried to explain anything new.

14
commits
12
pull requests
0
releases
commits by repo
REPO COMMITS rpg 8rust-postgres 3gitzette 1gitzette-dispatch 1spqr 1
github stars
pgdogdev/pgdog ★★★★★★★★★★ 4,279
rust-postgres/rust-postgres ★★★★★★★★★ 3,925
postgres-ai/database-lab-engine ★★★★★★☆☆☆☆ 2,444
rpg ☆☆☆☆☆☆☆☆☆ 222
gitzette ☆☆☆☆☆☆☆☆☆ 4
gitzette-dispatch ☆☆☆☆☆☆☆☆☆ 1
← Mar 30 – Apr 5 Apr 13 – Apr 19 →
gitzette @NikolayS on gitzette @NikolayS 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.