ANALYZE for statistics collection in PostgreSQL - Mini Project: Build & Apply

Using ANALYZE to Collect Table Statistics in PostgreSQL

📖 Scenario: You are a database administrator for a small online bookstore. You want to help PostgreSQL make better decisions when running queries by collecting up-to-date statistics about your book sales data.

🎯 Goal: Learn how to use the ANALYZE command in PostgreSQL to collect statistics on a table, which helps the database optimize query performance.

📋 What You'll Learn

Create a table named sales with columns id, book_title, and quantity.

Insert sample data into the sales table.

Use the ANALYZE command to collect statistics on the sales table.

Verify that statistics have been collected by querying the system catalog.

💡 Why This Matters

🌍 Real World

Database administrators regularly run ANALYZE to keep query performance fast by updating statistics.

💼 Career

Knowing how to collect and check statistics is essential for roles like database administrator and backend developer.

1

Create the sales table

Create a table called sales with these columns: id as an integer primary key, book_title as text, and quantity as integer.

PostgreSQL

-- Your code here to create the sales table

Hint

Use CREATE TABLE with the specified columns and types.

2

Insert sample data into sales

Insert these three rows into the sales table: (1, 'The Great Gatsby', 5), (2, '1984', 8), and (3, 'To Kill a Mockingbird', 3).

PostgreSQL

CREATE TABLE sales (
    id INTEGER PRIMARY KEY,
    book_title TEXT,
    quantity INTEGER
);
-- Your code here to insert sample data

Hint

Use a single INSERT INTO statement with multiple rows.

3

Run ANALYZE on the sales table

Write the SQL command to run ANALYZE on the sales table to collect statistics.

PostgreSQL

CREATE TABLE sales (
    id INTEGER PRIMARY KEY,
    book_title TEXT,
    quantity INTEGER
);

INSERT INTO sales (id, book_title, quantity) VALUES
(1, 'The Great Gatsby', 5),
(2, '1984', 8),
(3, 'To Kill a Mockingbird', 3);
-- Your code here to run ANALYZE on sales

Hint

Use the ANALYZE command followed by the table name.

4

Check collected statistics in pg_stat_all_tables

Write a query to select relname and last_analyze from pg_stat_all_tables where relname is 'sales'.

PostgreSQL

CREATE TABLE sales (
    id INTEGER PRIMARY KEY,
    book_title TEXT,
    quantity INTEGER
);

INSERT INTO sales (id, book_title, quantity) VALUES
(1, 'The Great Gatsby', 5),
(2, '1984', 8),
(3, 'To Kill a Mockingbird', 3);

ANALYZE sales;
-- Your code here to query pg_stat_all_tables for sales statistics

Hint

Use a SELECT statement with a WHERE clause filtering on relname.

Practice

1. What is the main purpose of the ANALYZE command in PostgreSQL?

easy

A. To create indexes on tables

B. To delete old data from tables

C. To backup the database

D. To collect statistics about tables for query planning

Solution

1. Step 1: Understand ANALYZE function

   The ANALYZE command collects statistics about the contents of tables.

2. Step 2: Purpose of statistics

   These statistics help the database decide the best way to run queries efficiently.

3. Final Answer:

   To collect statistics about tables for query planning -> Option D

4. Quick Check:

   ANALYZE = collect statistics [OK]

Hint: ANALYZE gathers table stats to improve query plans [OK]

Common Mistakes:

• Confusing ANALYZE with data deletion
• Thinking ANALYZE creates indexes
• Assuming ANALYZE backs up data

2. Which of the following is the correct syntax to run ANALYZE on a specific table named employees with detailed output?

easy

A. ANALYZE VERBOSE employees;

B. ANALYZE employees VERBOSE;

C. ANALYZE TABLE employees VERBOSE;

D. ANALYZE VERBOSE ON employees;

Solution

1. Step 1: Recall ANALYZE syntax

   The correct syntax is ANALYZE [VERBOSE] table_name; with VERBOSE before the table name.

2. Step 2: Check each option

   ANALYZE VERBOSE employees; matches the correct syntax exactly. Others have incorrect order or extra keywords.

3. Final Answer:

   ANALYZE VERBOSE employees; -> Option A

4. Quick Check:

   ANALYZE VERBOSE table_name; = ANALYZE VERBOSE employees; [OK]

Hint: VERBOSE goes right after ANALYZE before table name [OK]

Common Mistakes:

• Placing VERBOSE after table name
• Adding TABLE keyword (not used)
• Using ON keyword incorrectly

3. Given the following commands run in PostgreSQL:

ANALYZE VERBOSE employees;
ANALYZE sales;

What will be the output behavior?

medium

A. No output for either table

B. Detailed output for employees table, no output for sales table

C. Detailed output for both tables

D. Error because VERBOSE cannot be used with ANALYZE

Solution

1. Step 1: Understand VERBOSE effect

   Using VERBOSE with ANALYZE shows detailed progress messages for that command.

2. Step 2: Analyze commands separately

   The first command shows detailed output for employees. The second command runs normally without verbose output for sales.

3. Final Answer:

   Detailed output for employees table, no output for sales table -> Option B

4. Quick Check:

   VERBOSE shows details only when used [OK]

Hint: VERBOSE shows details only for that ANALYZE command [OK]

Common Mistakes:

• Expecting output for all ANALYZE commands
• Thinking VERBOSE causes errors
• Assuming no output means failure

4. You run ANALYZE VERBOSE mytable; but get an error: ERROR: relation "mytable" does not exist. What is the most likely cause?

medium

A. The table name is misspelled or does not exist

B. ANALYZE cannot be run with VERBOSE

C. You need to run ANALYZE on the whole database first

D. The database is in read-only mode

Solution

1. Step 1: Understand the error message

   The error says the relation (table) "mytable" does not exist, meaning PostgreSQL cannot find it.

2. Step 2: Identify common causes

   This usually happens if the table name is misspelled or the table was not created.

3. Final Answer:

   The table name is misspelled or does not exist -> Option A

4. Quick Check:

   Relation not found = wrong or missing table name [OK]

Hint: Check table name spelling if relation not found error appears [OK]

Common Mistakes:

• Thinking VERBOSE causes the error
• Assuming ANALYZE must run on whole database first
• Ignoring error details about relation

5. You want to improve query performance on a large table orders that changes frequently. Which approach using ANALYZE is best?

hard

A. Run ANALYZE VERBOSE orders; only once after creating the table

B. Run ANALYZE; on the whole database once a year

C. Run ANALYZE orders; regularly and use VERBOSE to monitor progress

D. Avoid running ANALYZE because it locks the table

Solution

1. Step 1: Consider table size and update frequency

   Large, frequently changing tables benefit from regular statistics updates to keep query plans accurate.

2. Step 2: Use ANALYZE regularly with VERBOSE

   Running ANALYZE orders; regularly updates stats. Adding VERBOSE helps monitor progress during analysis.

3. Step 3: Evaluate other options

   Running ANALYZE once a year is too infrequent. Running only once after creation misses ongoing changes. ANALYZE does not lock tables for long.

4. Final Answer:

   Run ANALYZE orders; regularly and use VERBOSE to monitor progress -> Option C

5. Quick Check:

   Regular ANALYZE keeps stats fresh for big tables [OK]

Hint: Regular ANALYZE keeps stats fresh; VERBOSE shows progress [OK]

Common Mistakes:

• Running ANALYZE too rarely
• Thinking ANALYZE locks tables extensively
• Ignoring VERBOSE usefulness for monitoring