/explore
|
You are here 
|
boringsql.com | ||
| | | | |
www.crunchydata.com
Adding extended statistics can add information about how columns are related. Louise has some real life example queries and tips for working with extended table stats that can dramatically improve query performance. |
|
| | | | | ||
| | | | |
phiresky.github.io
Did you know that PostgreSQL stores statistics about your data that can also be pretty useful not just for the query planner? Say you have a table users (id bigint, created timestamptz, category text): This information is a bit hard to interpret, so let's just let AI give us a nice visualization of |
|
| | | | | ||
| | | | |
jazco.dev
Postgres uses an internal table called 'pg_statistic' to keep track of some metadata on all tables in the DB. Postgres's Planner uses these statistics when estimating the cost of operations, which, if out of date, can cause the Planner to pick a suboptimal plan for our query. To trigger an update of 'pg_statistic' manually for a table, we can run 'ANALYZE' on it, helping the Planner estimate costs better and speeding up queries dramatically (in some cases). |
|
| | | | | ||
| | | | |
blog.jdboyd.net
|
|
| | | |||
