Courses
SQL Advanced: Queries That Hold Up Under Load
Check Yourself: Running It in Production
Five scenario questions on pruning, keys on partitioned tables, table rewrites, restore tests and dropping partitions. If you miss more than one, reread the lessons in this section.
Course content
Join this Course
Sign in to save your progress.
-
Reading Plans
-
EXPLAIN ANALYZE: Reading a Plan Line by Line
-
Statistics, ANALYZE and Why the Planner Guesses Wrong
-
-
-
Indexes That Earn Their Cost
-
B-tree, Partial and Expression Indexes
-
GIN, GiST and BRIN: When a B-tree Is the Wrong Tool
-
-
-
Concurrency
-
MVCC, VACUUM and Table Bloat
-
Locks, SELECT FOR UPDATE and Deadlocks
-
-
-
Advanced Query Shapes
-
Recursive CTEs and Hierarchies
-
JSONB: Query Semi-Structured Data Without Regretting It
-
-
-
Running It in Production
-
Partitioning Large Tables
-
Changing a Live Table Without Locking It
-
Backup, Restore and Proving the Restore Works
-
-
- Final Check: SQL Advanced
1.
sales_log is partitioned by month on sold_on. A query filters only on customer_id. What does the plan do?
2.
You try to create a primary key on sale_id alone on a table partitioned by sold_on. What happens?
3.
Which of these two column changes rewrites a big table, so that it blocks all access for a long time?
4.
A nightly pg_dump has been written for a year and was never restored. Which check proves the backup works?
5.
Why is dropping an old partition better than DELETE FROM sales_log WHERE sold_on is older than a date?
About
Five scenario questions on pruning, keys on partitioned tables, table rewrites, restore tests and dropping partitions. If you miss more than one, reread the lessons in this section.
- Duration
- 5 min
- Last update
- 09/23/2026
Was this helpful?
0
0
Comments (0)
Sign in to commentNo comments yet.