Pgtestdb's template cloning approach to testing is fast
peterldowns
19 points
2 comments
July 30, 2026
Related Discussions
Found 5 related stories in 58.3ms across 6,460 title embeddings via pgvector HNSW
- pgrust passes 100% of the Postgres regression tests tosh · 20 pts · July 11, 2026 · 52% similar
- Pgbot: A 5.9 MB read-only Postgres tool for humans and agents sashash · 47 pts · August 25, 2026 · 52% similar
- Postgres rewritten in Rust, now passing 100% of the Postgres regression tests SweetSoftPillow · 526 pts · July 09, 2026 · 49% similar
- Pgrust v0.2: Now faster than Postgres and Clickhouse Latest malisper · 18 pts · July 30, 2026 · 48% similar
- pg_clickhouse v0.10: Subquery pushdown and 1000x faster TPC-H queries saisrirampur · 49 pts · August 11, 2026 · 47% similar
Discussion Highlights (2 comments)
lukasschwab
> I’m going to add a recommendation in our docs for pgtestdb, particularly for users aiming to test end-to-end (i.e. job inserted by client → fully completed by worker). That's exactly what I did to learn River — implementing simple apps and testing their execution with pgtestdb: https://github.com/lukasschwab/river-playground The starter skeleton was LLM-generated and not quite perfect, but discovering the coding agent's mistakes was satisfying in its own right.
peterldowns
Just want to say thank you to Brandur for doing such a cool experiment. Last year I actually explored the River test suite to understand how they made it work so quickly — he's understating it when he says their implementation is "gold standard." I'm both surprised and excited to hear that pgtestdb, out of the box, can give anyone a ~nearly as fast experience. Going to have to throw some tokens at pooling... very interesting idea. Thank you, Brandur!