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

We're Looking for 10 dbt Developers to Test Relationship-Aware JOINs — 12 Months Free
0dev.to Data
The Best Disaster Recovery Solutions for Cross-Geography Replication (2026): Compared by What They Replicate
0dev.to Database

SQL Challenge: Can You Find the Second Purchase of Every Customer Using ROW_NUMBER()?
0dev.to Database

Database Migrations at Scale: How to Change Production Databases Without Breaking Applications
0dev.to Database

The Double-Booked Seat: Fixing a Booking Race Condition in Postgres
0dev.to Database

Preventing Duplicate Contact Names From Silently Corrupting Your Lending Ledger
0dev.to Database