Production query plans without production data

This site does not allow itself to be embedded. You can still read it on the original site — the toolbar below keeps your place in the directory.

In the previous article we covered how the PostgreSQL planner reads pg_class and pg_statistic to estimate row counts, choose join strategies, and decide whether an index scan is worth it. The message was clear: when statistics are wrong, everything else goes with it. Streaming replication provides bit-to-bit replication, so all replicas share the same statistics with primary server. But there was…

Read on boringsql.com ↗