Idézet:You already know how to keep MySQL alive in production. You've tuned InnoDB, chased deadlocks, and survived your fair share of late-night incident calls. Now you've been handed PostgreSQL-and you'd like to avoid relearning everything the hard way.

Thinking in PostgreSQL is a field guide for engineers who grew up on MySQL and now have to run Postgres in anger. It doesn't start from "what is a database?" and it doesn't pretend PostgreSQL is just a drop-in replacement. Instead, it focuses on the mental model shift

From threads in one big daemon to one process per connection and mandatory connection pooling.
From InnoDB's clustered primary key to Postgres's heap + separate indexes and real MVCC tuples.
From "purge will sort it out" to autovacuum, freezing, and transaction age as first-class concerns.
From AUTO_INCREMENT and REPLACE INTO to sequences, identity columns, and ON CONFLICT.
From hoping the slow query log tells you something useful to EXPLAIN (ANALYZE, BUFFERS) and pg_stat_* views.
The book is organized as a practical, production-oriented journey

Architecture & MVCC - how Postgres actually lays out data on disk, how MVCC works, why bloat happens, and how to keep autovacuum on your side.
Concurrency & Indexing - reading pg_stat_activity, understanding isolation levels, locks, and deadlocks, and designing indexes using partial, expression, covering, GIN, BRIN, and more.
Monitoring & High Availability - using the built-in statistics views, pg_stat_statements, streaming replication, WAL, replication slots, and point-in-time recovery instead of hoping backups work.
Advanced Features & Configuration - JSONB, window functions, partitioning, extensions, key configuration knobs, and the migration "gotchas" that surprise MySQL veterans most.
Throughout, the focus is vendor-neutral and operational: short SQL snippets you can paste into psql, checklists you can run weekly, and mental models that still make sense whether your Postgres is on-prem, in the cloud, behind a proxy, or sitting next to ClickHouse and MongoDB.

If you've ever caught yourself treating PostgreSQL like "MySQL with slightly different syntax," this book is your gentle intervention.

Idézet:? Mysql To Postgres.pdf (2.39 MB)