Why aggregation matters in PostgreSQL - Performance Analysis

Time Complexity: Why aggregation matters

O(n)

Understanding Time Complexity

When we use aggregation in databases, we combine many rows into summary results. Understanding how long this takes helps us know how well our queries will perform as data grows.

We want to see how the work needed changes when we have more data to aggregate.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT department, COUNT(*) AS employee_count
FROM employees
GROUP BY department;
    

This query counts how many employees are in each department by grouping rows with the same department.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning each row in the employees table once.
• How many times: Once for every employee row (n times).

How Execution Grows With Input

As the number of employees grows, the database must look at each one to count them by department.

Input Size (n)	Approx. Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The work grows directly with the number of rows; doubling rows doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the aggregation grows in a straight line with the number of rows.

Common Mistake

[X] Wrong: "Aggregation runs instantly no matter how much data there is."

[OK] Correct: The database must still look at every row to count or summarize, so more data means more work and more time.

Interview Connect

Knowing how aggregation scales helps you explain query performance clearly and shows you understand how databases handle large data sets.

Self-Check

"What if we added an index on the department column? How would the time complexity change?"

Practice

1. What is the main purpose of aggregation functions like COUNT or SUM in SQL?

easy

A. To summarize multiple rows into a single value

B. To delete duplicate rows from a table

C. To join two tables together

D. To create new tables from existing ones

Solution

1. Step 1: Understand aggregation functions

   Aggregation functions like COUNT and SUM take many rows and produce one summary value.

2. Step 2: Identify their purpose

   They help to reduce data by summarizing, not by deleting or joining tables.

3. Final Answer:

   To summarize multiple rows into a single value -> Option A

4. Quick Check:

   Aggregation = Summary [OK]

Hint: Aggregation means summarizing many rows into one value [OK]

Common Mistakes:

• Thinking aggregation deletes rows
• Confusing aggregation with JOIN
• Believing aggregation creates new tables

2. Which of the following is the correct syntax to count rows in a table named sales?

easy

A. SELECT COUNT ALL sales;

B. SELECT COUNT(*) FROM sales;

C. SELECT COUNT(sales) FROM *;

D. SELECT COUNT FROM sales();

Solution

1. Step 1: Recall correct COUNT syntax

   The correct syntax to count all rows is SELECT COUNT(*) FROM table_name;.

2. Step 2: Check each option

   SELECT COUNT(*) FROM sales; matches the correct syntax. Others have syntax errors or wrong order.

3. Final Answer:

   SELECT COUNT(*) FROM sales; -> Option B

4. Quick Check:

   COUNT(*) syntax = SELECT COUNT(*) FROM sales; [OK]

Hint: COUNT(*) counts all rows, use parentheses and star [OK]

Common Mistakes:

• Omitting parentheses after COUNT
• Using COUNT without * or column
• Wrong order of keywords

3. Given the table orders with columns customer_id and amount, what does this query return?

SELECT customer_id, SUM(amount) FROM orders GROUP BY customer_id;

medium

A. Total amount spent by each customer

B. List of all orders with amounts

C. Total amount spent by all customers combined

D. Number of orders per customer

Solution

1. Step 1: Understand GROUP BY usage

   GROUP BY customer_id groups rows by each customer.

2. Step 2: Understand SUM(amount)

   SUM(amount) adds all amounts per customer group.

3. Final Answer:

   Total amount spent by each customer -> Option A

4. Quick Check:

   GROUP BY + SUM = total per group [OK]

Hint: GROUP BY groups rows; SUM adds values per group [OK]

Common Mistakes:

• Thinking SUM returns total for all rows without grouping
• Confusing SUM with COUNT
• Ignoring GROUP BY effect

4. What is wrong with this query?

SELECT customer_id, COUNT(*) FROM orders;

medium

A. customer_id must be inside COUNT()

B. COUNT(*) cannot be used without WHERE

C. Missing GROUP BY clause for customer_id

D. SELECT must have ORDER BY with COUNT

Solution

1. Step 1: Check aggregation with non-aggregated column

   customer_id is selected but not aggregated or grouped.

2. Step 2: Identify missing GROUP BY

   To use COUNT(*) with customer_id, GROUP BY customer_id is required.

3. Final Answer:

   Missing GROUP BY clause for customer_id -> Option C

4. Quick Check:

   Non-aggregated columns need GROUP BY [OK]

Hint: Use GROUP BY when mixing columns with aggregation [OK]

Common Mistakes:

• Forgetting GROUP BY when selecting non-aggregated columns
• Thinking COUNT needs WHERE clause
• Assuming ORDER BY is mandatory with aggregation

5. You want to find the average order amount per customer but only for customers who placed more than 3 orders. Which query correctly achieves this?

hard

A. SELECT customer_id, AVG(amount) FROM orders WHERE COUNT(*) > 3 GROUP BY customer_id;

B. SELECT customer_id, AVG(amount) FROM orders HAVING COUNT(*) > 3 GROUP BY customer_id;

C. SELECT customer_id, AVG(amount) FROM orders GROUP BY customer_id WHERE COUNT(*) > 3;

D. SELECT customer_id, AVG(amount) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3;

Solution

1. Step 1: Understand filtering groups with HAVING

   HAVING filters groups after aggregation; WHERE filters rows before aggregation.

2. Step 2: Check query order and clauses

   SELECT customer_id, AVG(amount) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3; correctly uses GROUP BY then HAVING COUNT(*) > 3 to filter customers with more than 3 orders.

3. Final Answer:

   SELECT customer_id, AVG(amount) FROM orders GROUP BY customer_id HAVING COUNT(*) > 3; -> Option D

4. Quick Check:

   Use HAVING to filter groups after GROUP BY [OK]

Hint: Use HAVING to filter groups, not WHERE [OK]

Common Mistakes:

• Using WHERE to filter aggregated counts
• Placing HAVING before GROUP BY
• Syntax errors mixing WHERE and HAVING