Extended Statistics in Postgres

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.

Something you probably already know about Postgres: The planner needs to know things about the data to come up with a good access plan. For example, it needs to decide whether to use an index or a sequential scan. It’s looking at things like row count or distinct values when it comes up with this plan. The statistics it uses to do this are stored internally. One place is the pg_class table.

Read on valerieparhamthompson.com ↗