Database
Chris van Eijk: Deleting one tenant in PostgreSQL: cascade, batch or DROP
Planet PostgreSQL0 views
Deleting one tenant from a shared PostgreSQL 17 database, measured: cascade, batches or dropping a partition; locks, batch size, disk space, what stays behind.
Source:https://postgr.es/p/9xjPreviousChris van Eijk: Unique per tenant in PostgreSQL: soft delete and RLS leaksNextHarness bought Augment’s coding agents. The best feature hasn’t shipped yet.
Related posts
LlamaIndex Workflows vs LangGraph: Event-Driven Architecture and Async State Overhead Showdown
0dev.to Programming

Rider and Databases: Lesser-Known IDE Features That Save Time
0dev.to Database
KivaDB v2: What's Coming and How You Can Contribute
0dev.to Database
Your LLM cost log says $0.00. The invoice says $1,320.
0dev.to Database
SQLite in Production: A Practical Setup with Litestream Backups
0dev.to Database
The Scariest Part of "Skynet Mode" Is Your Own Unauthenticated Endpoint
0dev.to Security