Bird
Raised Fist0
PostgreSQLquery~5 mins

INSERT ON CONFLICT (upsert) in PostgreSQL - Time & Space Complexity

Choose your learning style10 modes available
LearnWhyDeepVisualTryChallengeProjectRecallTime
Time Complexity: INSERT ON CONFLICT (upsert)
O(log n)
Understanding Time Complexity

When we use INSERT ON CONFLICT in PostgreSQL, we want to add new data or update existing data without duplicates.

We ask: How does the time to do this grow as the data gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.


INSERT INTO users (id, name, email)
VALUES (1, 'Alice', 'alice@example.com')
ON CONFLICT (id) DO UPDATE
SET name = EXCLUDED.name, email = EXCLUDED.email;

This code tries to insert a user. If the user id already exists, it updates the name and email instead.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

  • Primary operation: Searching for a matching row by the conflict key (id).
  • How many times: Once per insert or update operation.
How Execution Grows With Input

As the table grows, finding if the id exists takes longer if no index is used.

Input Size (n)Approx. Operations
10About 10 checks if no index
100About 100 checks if no index
1000About 1000 checks if no index

Pattern observation: Without an index, the search grows linearly with table size. With an index, it stays fast.

Final Time Complexity

Time Complexity: O(log n)

This means the time to insert or update grows slowly as the table grows, thanks to the index.

Common Mistake

[X] Wrong: "INSERT ON CONFLICT always takes the same time no matter the table size."

[OK] Correct: Without an index on the conflict column, the database must scan more rows as the table grows, making it slower.

Interview Connect

Understanding how upsert works and its time cost shows you know how databases handle data efficiently, a useful skill in many projects.

Self-Check

"What if we removed the index on the conflict column? How would the time complexity change?"

Practice

(1/5)
1. What does the INSERT ON CONFLICT clause do in PostgreSQL?
easy
A. It inserts a new row or updates existing row if a conflict occurs.
B. It deletes rows that conflict with the new data.
C. It only inserts new rows and ignores conflicts without any update.
D. It creates a new table if a conflict is found.

Solution

  1. Step 1: Understand the purpose and behavior of INSERT ON CONFLICT

    This clause helps handle duplicate key conflicts during insert operations by allowing an update instead of error. It either updates the existing row or ignores the insert, preventing errors.

  2. Final Answer:

    It inserts a new row or updates existing row if a conflict occurs. -> Option A

  3. Quick Check:

    INSERT ON CONFLICT = Insert or update [OK]
Hint: Think: insert new or update existing on conflict [OK]
Common Mistakes:
  • Confusing ON CONFLICT with DELETE
  • Assuming it only inserts without update
  • Thinking it creates new tables
2. Which of the following is the correct syntax to update a column price on conflict for a table products with unique id?
easy
A. INSERT INTO products (id, price) VALUES (1, 100) ON CONFLICT DO NOTHING;
B. INSERT INTO products (id, price) VALUES (1, 100) ON DUPLICATE KEY UPDATE price = price + 1;
C. INSERT INTO products (id, price) VALUES (1, 100) ON CONFLICT (id) DO UPDATE SET price = EXCLUDED.price;
D. INSERT INTO products (id, price) VALUES (1, 100) ON CONFLICT (id) DO DELETE;

Solution

  1. Step 1: Check PostgreSQL syntax for upsert and identify correct usage of EXCLUDED

    PostgreSQL uses ON CONFLICT (column) DO UPDATE SET with EXCLUDED to refer to new values. INSERT INTO products (id, price) VALUES (1, 100) ON CONFLICT (id) DO UPDATE SET price = EXCLUDED.price; correctly uses EXCLUDED.price to update the price on conflict of id.

  2. Final Answer:

    INSERT INTO products (id, price) VALUES (1, 100) ON CONFLICT (id) DO UPDATE SET price = EXCLUDED.price; -> Option C

  3. Quick Check:

    Correct syntax uses ON CONFLICT (id) DO UPDATE SET with EXCLUDED [OK]
Hint: Use EXCLUDED.column to update on conflict [OK]
Common Mistakes:
  • Using MySQL syntax ON DUPLICATE KEY
  • Forgetting EXCLUDED keyword
  • Using DO DELETE which is invalid
3. Given the table users(id INT PRIMARY KEY, name TEXT, age INT) with data:
(1, 'Alice', 30)
What will be the result of this query?
INSERT INTO users (id, name, age) VALUES (1, 'Alice', 31) ON CONFLICT (id) DO UPDATE SET age = EXCLUDED.age RETURNING *;
medium
A. [] (empty result)
B. [{id:1, name:'Alice', age:31}]
C. Error: duplicate key value violates unique constraint
D. [{id:1, name:'Alice', age:30}]

Solution

  1. Step 1: Understand the existing data/conflict and apply ON CONFLICT DO UPDATE

    Row with id=1 exists with age=30, new insert tries age=31 causing conflict on id. It updates age to EXCLUDED.age (31) and returns the updated row.

  2. Final Answer:

    [{id:1, name:'Alice', age:31}] -> Option B

  3. Quick Check:

    ON CONFLICT updates age to 31 and returns updated row [OK]
Hint: ON CONFLICT updates existing row and returns it [OK]
Common Mistakes:
  • Expecting error on duplicate key
  • Thinking old age remains unchanged
  • Assuming empty result on update
4. Identify the error in this query:
INSERT INTO inventory (product_id, quantity) VALUES (10, 5) ON CONFLICT (product_id) DO UPDATE quantity = quantity + EXCLUDED.quantity;
medium
A. VALUES clause cannot be used with ON CONFLICT.
B. EXCLUDED keyword is not allowed in DO UPDATE.
C. ON CONFLICT must be followed by DO NOTHING, not DO UPDATE.
D. Missing SET keyword before update expressions.

Solution

  1. Step 1: Review ON CONFLICT DO UPDATE syntax and identify missing SET keyword

    The DO UPDATE clause requires SET keyword before specifying column updates. The query misses SET before 'quantity = quantity + EXCLUDED.quantity', causing syntax error.

  2. Final Answer:

    Missing SET keyword before update expressions. -> Option D

  3. Quick Check:

    DO UPDATE requires SET before column assignments [OK]
Hint: Remember DO UPDATE SET column = value [OK]
Common Mistakes:
  • Omitting SET keyword in DO UPDATE
  • Misusing EXCLUDED keyword
  • Confusing DO NOTHING and DO UPDATE
5. You want to insert a new user into users(id, name, score) but if the id exists, update the score only if the new score is higher. Which query correctly implements this?
hard
A. INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO UPDATE SET score = EXCLUDED.score WHERE EXCLUDED.score > users.score;
B. INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO UPDATE SET score = users.score WHERE EXCLUDED.score > users.score;
C. INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO NOTHING WHERE EXCLUDED.score > users.score;
D. INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO UPDATE SET score = EXCLUDED.score;

Solution

  1. Step 1: Understand conditional update on conflict and use WHERE clause in DO UPDATE

    You want to update score only if new score is greater than existing score. INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO UPDATE SET score = EXCLUDED.score WHERE EXCLUDED.score > users.score; uses WHERE EXCLUDED.score > users.score to conditionally update score correctly.

  2. Final Answer:

    INSERT INTO users (id, name, score) VALUES (2, 'Bob', 50) ON CONFLICT (id) DO UPDATE SET score = EXCLUDED.score WHERE EXCLUDED.score > users.score; -> Option A

  3. Quick Check:

    Conditional update uses WHERE clause in DO UPDATE [OK]
Hint: Use WHERE in DO UPDATE for conditional changes [OK]
Common Mistakes:
  • Updating unconditionally without WHERE
  • Using DO NOTHING with WHERE (invalid)
  • Setting score to old value mistakenly
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard