Why views matter in PostgreSQL - Performance Analysis

Time Complexity: Why views matter in PostgreSQL

O(n)

Understanding Time Complexity

When using views in PostgreSQL, it's important to understand how the time to get results changes as data grows.

We want to know how using a view affects the speed of queries as the database gets bigger.

Scenario Under Consideration

Analyze the time complexity of querying a simple view.

CREATE VIEW recent_orders AS
  SELECT order_id, customer_id, order_date
  FROM orders
  WHERE order_date > CURRENT_DATE - INTERVAL '30 days';

SELECT * FROM recent_orders WHERE customer_id = 123;
    

This view selects orders from the last 30 days. The query fetches recent orders for one customer.

Identify Repeating Operations

Look at what repeats when running the query.

• Primary operation: Scanning the orders table to find rows matching the date and customer filters.
• How many times: Once per query, but the scan checks many rows depending on table size.

How Execution Grows With Input

As the orders table grows, the number of rows to check grows too.

Input Size (n)	Approx. Operations
10	About 10 rows scanned
100	About 100 rows scanned
1000	About 1000 rows scanned

Pattern observation: The work grows roughly in direct proportion to the number of rows in the table.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows linearly with the number of rows in the orders table.

Common Mistake

[X] Wrong: "Using a view makes queries run instantly regardless of data size."

[OK] Correct: A view is just a saved query. It still runs on the underlying data, so bigger tables mean more work.

Interview Connect

Understanding how views affect query time helps you explain database design choices clearly and confidently.

Self-Check

"What if the orders table had an index on order_date? How would that change the time complexity?"

Practice

1. What is the main purpose of using a VIEW in PostgreSQL?

easy

A. To save a complex query as a reusable object

B. To permanently store data separately from tables

C. To speed up data insertion into tables

D. To delete rows from multiple tables at once

Solution

1. Step 1: Understand what a VIEW is

   A VIEW in PostgreSQL is a saved SQL query that acts like a virtual table.

2. Step 2: Identify the main use of a VIEW

   It simplifies complex queries by letting you reuse them without rewriting.

3. Final Answer:

   To save a complex query as a reusable object -> Option A

4. Quick Check:

   Views simplify queries = A [OK]

Hint: Views store queries, not data, for easy reuse [OK]

Common Mistakes:

• Thinking views store data separately
• Confusing views with tables
• Assuming views speed up inserts

2. Which of the following is the correct syntax to create a view named active_users showing users with status = 'active'?

easy

A. CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active';

B. CREATE active_users VIEW AS SELECT * FROM users WHERE status = 'active';

C. VIEW CREATE active_users AS SELECT * FROM users WHERE status = 'active';

D. CREATE VIEW active_users SELECT * FROM users WHERE status = 'active';

Solution

1. Step 1: Recall the correct CREATE VIEW syntax

   The syntax is: CREATE VIEW view_name AS SELECT ...

2. Step 2: Match the syntax with options

   CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active'; matches the correct syntax exactly.

3. Final Answer:

   CREATE VIEW active_users AS SELECT * FROM users WHERE status = 'active'; -> Option A

4. Quick Check:

   CREATE VIEW ... AS SELECT ... = B [OK]

Hint: Remember: CREATE VIEW name AS SELECT ... [OK]

Common Mistakes:

• Swapping keywords CREATE and VIEW
• Omitting AS keyword
• Incorrect keyword order

3. Given the table orders with columns id, customer, and amount, what will this view return?

CREATE VIEW big_orders AS SELECT customer, amount FROM orders WHERE amount > 100;

Then running:

SELECT * FROM big_orders;

medium

A. Syntax error because id is missing in view

B. All orders showing id, customer, and amount

C. All orders with amount greater than 100 showing customer and amount

D. Only orders with amount less than or equal to 100

Solution

1. Step 1: Understand the view definition

   The view selects customer and amount from orders where amount is greater than 100.

2. Step 2: Predict the SELECT * from the view

   It returns only customer and amount columns for orders with amount > 100.

3. Final Answer:

   All orders with amount greater than 100 showing customer and amount -> Option C

4. Quick Check:

   View filters amount > 100 and selects customer, amount = D [OK]

Hint: View columns = selected columns, filtered by WHERE [OK]

Common Mistakes:

• Expecting all columns to appear
• Confusing filter condition direction
• Thinking missing columns cause errors

4. You created a view with:

CREATE VIEW recent_sales AS SELECT * FROM sales WHERE sale_date > CURRENT_DATE - INTERVAL '7 days';

But running SELECT * FROM recent_sales; returns an error. What is the likely cause?

medium

A. CURRENT_DATE cannot be used in a view definition

B. The view definition is correct; error is elsewhere

C. The view needs to be refreshed manually to update data

D. The INTERVAL syntax is invalid in the view definition

Solution

1. Step 1: Check if INTERVAL and CURRENT_DATE are valid

   Both INTERVAL and CURRENT_DATE are valid in PostgreSQL and can be used in views.

2. Step 2: Understand view behavior

   Views are virtual and always reflect current data; no manual refresh needed.

3. Final Answer:

   The view definition is correct; error is elsewhere -> Option B

4. Quick Check:

   Valid syntax means error is not in view code = A [OK]

Hint: Check error source; valid syntax means problem is outside view [OK]

Common Mistakes:

• Assuming CURRENT_DATE is disallowed in views
• Thinking views store data needing refresh
• Blaming INTERVAL syntax without checking error message

5. You want to restrict users to see only active employees' names and departments without exposing salaries. Which approach using views is best?

hard

A. Create a view selecting name, department, and salary for all employees

B. Create a view selecting all columns but filter status = 'active'

C. Create a view selecting only salary and status columns

D. Create a view selecting only name and department from employees where status = 'active'

Solution

1. Step 1: Identify data to expose

   Only active employees' names and departments should be visible, no salaries.

2. Step 2: Choose view that filters and limits columns

   Create a view selecting only name and department from employees where status = 'active' selects only needed columns and filters active status, protecting salary data.

3. Final Answer:

   Create a view selecting only name and department from employees where status = 'active' -> Option D

4. Quick Check:

   View limits columns and filters rows = C [OK]

Hint: Select only needed columns and filter rows in view [OK]

Common Mistakes:

• Including salary column exposing sensitive data
• Not filtering active status
• Selecting all columns unnecessarily