Database
Chris van Eijk: Counting per tenant in PostgreSQL: count, estimate, counter
Planet PostgreSQL0 views
count(*) per tenant in PostgreSQL 17, measured: why it got 5× slower for the largest tenant, when estimates are wrong, and what a counter row costs under load.
Source:https://postgr.es/p/9x6PreviousTomas Vondra: Are we reverting patches because of bugs found by AI?NextChris van Eijk: Audit log per tenant in PostgreSQL: what a trigger costs
Related posts
A Practical Stack Checklist for Small-Business Web Apps (Next.js, Node.js, SQL or MongoDB)
0dev.to Node

In an audit, a green test means the bug is real
0dev.to Testing
Fix Go Goroutine Leaks & Scale ClickHouse Monoliths
0dev.to Go
96 rows out of 47,114: when 92% of your joins return nothing and 97% of the rest return the wrong match
0dev.to Database
MoL-SQL: A Controlled Benchmark for Mixture-of-Language Text-to-SQL
0arXiv cs.DB
Device-Centric Cooperative Floor-Level Estimation under Sparse Anchor Deployment for Construction-Site Applications
0arXiv eess.SP