RETURNING clause mental model in PostgreSQL - Time & Space Complexity

Time Complexity: RETURNING clause mental model

O(n)

Understanding Time Complexity

We want to understand how the time needed to run a query with a RETURNING clause changes as the data grows.

Specifically, how does adding RETURNING affect the work the database does?

Scenario Under Consideration

Analyze the time complexity of this PostgreSQL query using RETURNING.

INSERT INTO employees (name, department) 
VALUES ('Alice', 'Sales'), ('Bob', 'HR'), ('Carol', 'IT')
RETURNING id, name;
    

This query inserts multiple rows and returns the new ids and names of those rows.

Identify Repeating Operations

Look for repeated work inside the query.

• Primary operation: Inserting each row one by one.
• How many times: Once per row inserted.
• Additional operation: Returning the requested columns for each inserted row.
• How many times: Also once per inserted row.

How Execution Grows With Input

As the number of rows inserted grows, the work grows too.

Input Size (n)	Approx. Operations
10	About 10 inserts + 10 returns
100	About 100 inserts + 100 returns
1000	About 1000 inserts + 1000 returns

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

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows linearly with the number of rows inserted and returned.

Common Mistake

[X] Wrong: "RETURNING just adds a tiny fixed cost, so it doesn't grow with more rows."

[OK] Correct: The database must return data for each row inserted, so the work grows with the number of rows, not fixed.

Interview Connect

Understanding how RETURNING affects query time helps you explain performance clearly and shows you know how databases handle data flow.

Self-Check

"What if we used RETURNING * to return all columns instead of just a few? How would the time complexity change?"

Practice

1. What is the main purpose of the RETURNING clause in PostgreSQL?

easy

A. To create a new table based on existing data

B. To return data from rows affected by INSERT, UPDATE, or DELETE in the same query

C. To backup the database automatically after changes

D. To schedule queries to run at a later time

Solution

1. Step 1: Understand the role of RETURNING clause

   The RETURNING clause is used to get data from rows that are changed by INSERT, UPDATE, or DELETE commands.

2. Step 2: Compare options with this role

   Only To return data from rows affected by INSERT, UPDATE, or DELETE in the same query correctly describes this behavior. Other options describe unrelated features.

3. Final Answer:

   To return data from rows affected by INSERT, UPDATE, or DELETE in the same query -> Option B

4. Quick Check:

   RETURNING returns changed rows data [OK]

Hint: RETURNING gives changed rows data immediately [OK]

Common Mistakes:

• Thinking RETURNING creates tables
• Confusing RETURNING with backup or scheduling
• Assuming RETURNING only works with SELECT

2. Which of the following is the correct syntax to use the RETURNING clause after an INSERT statement?

easy

A. INSERT INTO table_name RETURNING * VALUES (...);

B. RETURNING * INSERT INTO table_name VALUES (...);

C. INSERT INTO table_name VALUES (...) RETURNING *;

D. INSERT INTO table_name VALUES (...) OUTPUT *;

Solution

1. Step 1: Recall correct RETURNING syntax

   In PostgreSQL, RETURNING comes after the VALUES clause in an INSERT statement.

2. Step 2: Check each option

   'INSERT INTO table_name VALUES (...) RETURNING *;' correctly places RETURNING after VALUES. Placing RETURNING between table_name and VALUES is incorrect order. Starting the statement with RETURNING is invalid. Using OUTPUT instead of RETURNING is SQL Server syntax, not PostgreSQL.

3. Final Answer:

   INSERT INTO table_name VALUES (...) RETURNING *; -> Option C

4. Quick Check:

   RETURNING follows VALUES in INSERT [OK]

Hint: RETURNING always comes after VALUES in INSERT [OK]

Common Mistakes:

• Placing RETURNING before VALUES
• Using OUTPUT instead of RETURNING
• Putting RETURNING before INSERT

3. Given the table users(id SERIAL PRIMARY KEY, name TEXT, age INT), what will this query return?

UPDATE users SET age = age + 1 WHERE name = 'Alice' RETURNING id, age;

medium

A. The id and new age of all users named 'Alice' after increment

B. The id and old age of all users named 'Alice' before increment

C. All rows in the users table with updated ages

D. An error because RETURNING cannot be used with UPDATE

Solution

1. Step 1: Understand UPDATE with RETURNING

   UPDATE changes rows matching the condition and RETURNING returns specified columns from those updated rows after the change.

2. Step 2: Analyze the query

   The query increments age by 1 for users named 'Alice' and returns their id and new age values.

3. Final Answer:

   The id and new age of all users named 'Alice' after increment -> Option A

4. Quick Check:

   RETURNING shows updated rows data [OK]

Hint: RETURNING shows updated values, not old ones [OK]

Common Mistakes:

• Thinking RETURNING shows old values
• Assuming it returns all rows, not just updated
• Believing RETURNING is invalid with UPDATE

4. Consider this DELETE query:

DELETE FROM orders WHERE order_date < '2023-01-01' RETURNING order_id;

Which of the following is a common mistake that would cause this query to fail?

medium

A. Writing RETURNING before WHERE clause

B. Using DELETE without WHERE clause

C. Using RETURNING without specifying columns

D. Using RETURNING with SELECT statement

Solution

1. Step 1: Check correct RETURNING placement

   RETURNING must come after the WHERE clause in DELETE statements.

2. Step 2: Identify the error in options

   Writing RETURNING before WHERE clause describes placing RETURNING before WHERE, which is invalid syntax and causes failure.

3. Final Answer:

   Writing RETURNING before WHERE clause -> Option A

4. Quick Check:

   RETURNING comes after WHERE in DELETE [OK]

Hint: RETURNING always follows WHERE clause [OK]

Common Mistakes:

• Putting RETURNING before WHERE
• Omitting columns in RETURNING (allowed but returns all columns)
• Using RETURNING with SELECT (invalid)
• Deleting without WHERE (allowed but risky)

5. You want to insert multiple rows into a products table and immediately get the generated product_id and price of each inserted row. Which query correctly uses the RETURNING clause to achieve this?

hard

A. INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) RETURN product_id, price;

B. INSERT INTO products (name, price) RETURNING product_id, price VALUES ('Pen', 1.5), ('Book', 10);

C. INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) OUTPUT product_id, price;

D. INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) RETURNING product_id, price;

Solution

1. Step 1: Recall correct syntax for multi-row INSERT with RETURNING

   RETURNING clause comes after all VALUES and specifies columns to return.

2. Step 2: Evaluate each option

   INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) RETURNING product_id, price; correctly places RETURNING after VALUES with correct columns. INSERT INTO products (name, price) RETURNING product_id, price VALUES ('Pen', 1.5), ('Book', 10); has wrong order. INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) OUTPUT product_id, price; uses OUTPUT which is not PostgreSQL syntax. INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) RETURN product_id, price; uses RETURN which is invalid.

3. Final Answer:

   INSERT INTO products (name, price) VALUES ('Pen', 1.5), ('Book', 10) RETURNING product_id, price; -> Option D

4. Quick Check:

   RETURNING after VALUES returns inserted rows data [OK]

Hint: RETURNING follows VALUES and lists columns to return [OK]

Common Mistakes:

• Placing RETURNING before VALUES
• Using OUTPUT instead of RETURNING
• Using RETURN instead of RETURNING