You have a large logs table with millions of rows. You want to improve query speed for recent logs and easily drop old logs. Which partitioning strategy is best?

hard📝 Application Q15 of 15

PostgreSQL - Table Partitioning

You have a large logs table with millions of rows. You want to improve query speed for recent logs and easily drop old logs. Which partitioning strategy is best?

ANo partitioning, just add indexes

BHash partitioning by log message content

CRange partitioning by log date, creating monthly partitions

DList partitioning by log severity levels

Step-by-Step Solution

Solution:

Step 1: Understand the data and goals
Logs are time-based; queries focus on recent data and dropping old data is needed.
Step 2: Choose partitioning strategy
Range partitioning by date with monthly partitions allows fast queries on recent logs and easy removal of old partitions.
Final Answer:
Range partitioning by log date, creating monthly partitions -> Option C
Quick Check:
Time-based data = range partitioning [OK]

Quick Trick: Use range partitions by date for time-based data [OK]

Common Mistakes:

Choosing hash partitioning for time-based queries
Using list partitioning on severity which doesn't help date queries
Skipping partitioning and relying only on indexes

Master "Table Partitioning" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

You have a large logs table with millions of rows. You want to improve query speed for recent logs and easily drop old logs. Which partitioning strategy is best?

Step 1: Understand the data and goals

Step 2: Choose partitioning strategy

Final Answer:

Quick Check:

Want More Practice?