/explore
|
You are here 
|
boringsql.com | ||
| | | | |
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 | |
| | | | |
postgrespro.com
|
|
| | | | | In previous articles we discussed query execution stages and statistics . Last time, I started on data access methods, namely Sequential scan . Today we will cover Index Scan. This article requires a basic understanding of the index method interface. If words like "operator class" and "access method properties" don't ring a bell, check out my article on indexes from a while back for a refresher. Plain Index Scan Indexes return row version IDs (tuple IDs, or TIDs for short), which can be handled in one 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). | |
| | | | |
128bit.io
|
|
| | | One of the things that really gets me excited about my new job is being able to use new technology. Sure, sometimes new technology is risky but I see groups befitting more then failing due to usingnewer technology. As always when talking about new technology, NoSQL seems to come up because there are a good number of people switching parts (or all) of theirapplication to use NoSQL databases to get by limits or to help withscalability issues. | ||
