Bitmap scans
If you only select a few rows, Postgre will decide on an index scan – if you select a majority of them, Postgre will decide on a table scan. But what if you read too much for an index scan to be efficient but too little for a sequential scan? The solution to the problem is to use a bitmap scan. This way, a single block is only used once during a scan. Postgre will first scan the index and compile those rows / blocks, which are needed at the end of the scan. Then Postgre will take this list and go to the table to really fetch those rows.
10
17 reads
Similar ideas to Bitmap scans
Order in Multi-Column Index Matters
Order of the columns matter.
The index is useless if the first column doesn't appear in the WHERE clause.
Example 1:
An index on (t, x) will not be used in this query:
- SELECT * FROM table WHERE...
Account for your hours: The Time Blocking method
The Time Blocking productivity method compels you to plan your day hour by hour, and prevent multitasking by batching similar tasks together.
- Make a to-do list for the day.
- Categorize hour tasks together in similar blocks.
- Esti...
Harmful things add up too
When you complain every day, eat junk food, and never work out, those things add up too. That’s how we become miserable. You almost never hear about how one single moment destroyed a person’s life. Of course, tragedies happen. But for the majority of us, we simply let lif...
Read & Learn
20x Faster
without
deepstash
with
deepstash
with
deepstash
Personalized microlearning
—
100+ Learning Journeys
—
Access to 200,000+ ideas
—
Access to the mobile app
—
Unlimited idea saving
—
—
Unlimited history
—
—
Unlimited listening to ideas
—
—
Downloading & offline access
—
—
Supercharge your mind with one idea per day
Enter your email and spend 1 minute every day to learn something new.
I agree to receive email updates