Tag: database

This is a classic reference for understanding PostgreSQL below the SQL surface. Query processing, storage, concurrency, and transaction behavior become much less mysterious when the internals are visible.

Keeping the original http URL is intentional because that is the source that resolves. This is reference material, not a polished marketing page.

This belongs in the queue because database performance is often where application assumptions meet physical reality. Indexes, query plans, and access patterns are product concerns when latency becomes user-visible.

It is also a reminder that "the database is slow" is rarely a useful diagnosis. The question is what the query asked the database to do.

This is useful because data modeling is still one of the quiet foundations of analytics, ML, and application design. Good models make downstream work boring in the best way.

The link is older in spirit than the AI material, but that is exactly why it belongs here. New tools keep inheriting old modeling mistakes.

This is a good systems explanation for software developers who use databases every day but have not built a mental model of parsing, planning, storage, indexes, and execution.

Worth keeping because better database intuition changes how you design APIs, migrations, reports, and data products.