Numeric and decimal precision in PostgreSQL - Time & Space Complexity

Time Complexity: Numeric and decimal precision

O(n)

Understanding Time Complexity

When working with numbers in a database, the precision of numeric and decimal types affects how calculations are done.

We want to understand how the time to process these numbers changes as their size or precision grows.

Scenario Under Consideration

Analyze the time complexity of the following SQL snippet that sums decimal numbers with precision.

SELECT SUM(price) 
FROM products
WHERE price > 0;
    

This query adds up all positive prices stored as numeric or decimal values.

Identify Repeating Operations

Look for repeated actions that affect time.

• Primary operation: Adding each price value one by one.
• How many times: Once for every row with a positive price.

How Execution Grows With Input

As the number of rows increases, the total additions increase too.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

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

Final Time Complexity

Time Complexity: O(n)

This means the time to sum prices grows in a straight line as the number of prices increases.

Common Mistake

[X] Wrong: "Adding numbers with more decimal places takes longer time per addition."

[OK] Correct: While precision affects storage, the addition operation time is mostly affected by how many numbers are added, not their decimal length.

Interview Connect

Understanding how numeric precision impacts query time helps you explain performance in real projects where money or measurements matter.

Self-Check

"What if we changed the query to multiply prices instead of summing? How would the time complexity change?"

Practice

1. What does the scale represent in a NUMERIC(10, 3) data type in PostgreSQL?

easy

A. The number of digits after the decimal point

B. The total number of digits allowed

C. The number of digits before the decimal point

D. The maximum value allowed

Solution

1. Step 1: Understand NUMERIC precision and scale

   In NUMERIC(precision, scale), precision is total digits, scale is digits after decimal.

2. Step 2: Apply to NUMERIC(10, 3)

   Here, scale = 3 means 3 digits after decimal point.

3. Final Answer:

   The number of digits after the decimal point -> Option A

4. Quick Check:

   Scale = digits after decimal [OK]

Hint: Scale is digits after decimal point in NUMERIC [OK]

Common Mistakes:

• Confusing scale with precision
• Thinking scale is digits before decimal
• Assuming scale limits total digits

2. Which of the following is the correct syntax to define a column named price with 7 digits total and 2 digits after the decimal in PostgreSQL?

easy

A. price DECIMAL(7)

B. price NUMERIC(2,7)

C. price DECIMAL(2,7)

D. price NUMERIC(7,2)

Solution

1. Step 1: Recall NUMERIC/DECIMAL syntax

   Syntax is NUMERIC(precision, scale) where precision >= scale.

2. Step 2: Match precision=7 and scale=2

   price NUMERIC(7,2) uses NUMERIC(7,2) which means 7 total digits, 2 after decimal.

3. Final Answer:

   price NUMERIC(7,2) -> Option D

4. Quick Check:

   NUMERIC(precision, scale) = NUMERIC(7,2) [OK]

Hint: Precision first, scale second in NUMERIC/DECIMAL [OK]

Common Mistakes:

• Swapping precision and scale
• Using scale larger than precision
• Omitting scale when needed

3. Given the table products(price NUMERIC(5,2)), what will be the stored value after inserting INSERT INTO products(price) VALUES (123.4567);?

medium

A. 123.45

B. 123.46

C. 123.4567

D. Error: value too precise

Solution

1. Step 1: Understand NUMERIC(5,2) limits

   Precision 5 means total 5 digits, scale 2 means 2 digits after decimal.

2. Step 2: Round input 123.4567 to 2 decimal places

   123.4567 rounds to 123.46 to fit scale 2.

3. Final Answer:

   123.46 -> Option B

4. Quick Check:

   Rounded to 2 decimals = 123.46 [OK]

Hint: NUMERIC rounds to scale digits on insert [OK]

Common Mistakes:

• Expecting truncation instead of rounding
• Assuming error on extra decimals
• Ignoring precision limits

4. You defined a column as amount NUMERIC(4,2). You try to insert 999.99 but get an error. What is the problem?

medium

A. NUMERIC cannot store decimal values

B. The scale 2 is too small for the value

C. The value exceeds the total precision of 4 digits

D. Syntax error in column definition

Solution

1. Step 1: Calculate digits in 999.99

   999.99 has 5 digits total (3 before decimal + 2 after).

2. Step 2: Compare with NUMERIC(4,2)

   NUMERIC(4,2) allows only 4 digits total, so 999.99 is too large.

3. Final Answer:

   The value exceeds the total precision of 4 digits -> Option C

4. Quick Check:

   Value digits > precision causes error [OK]

Hint: Total digits must fit precision, not just decimals [OK]

Common Mistakes:

• Thinking scale limits integer part
• Believing NUMERIC disallows decimals
• Ignoring precision limits

5. You want to store monetary values up to 999999.999 with exact precision in PostgreSQL. Which column definition is best to avoid rounding errors and allow this range?

hard

A. amount NUMERIC(9,3)

B. amount NUMERIC(6,3)

C. amount DECIMAL(9,2)

D. amount FLOAT(9)

Solution

1. Step 1: Determine needed precision and scale

   Value 999999.999 has 6 digits before decimal, 3 after, total 9 digits.

2. Step 2: Choose NUMERIC with precision 9 and scale 3

   NUMERIC(9,3) stores exactly 9 digits total with 3 decimals, matching requirement.

3. Step 3: Avoid FLOAT for exact money values

   FLOAT is approximate, may cause rounding errors.

4. Final Answer:

   amount NUMERIC(9,3) -> Option A

5. Quick Check:

   Exact money storage needs NUMERIC(9,3) [OK]

Hint: Use NUMERIC with precision = digits total, scale = decimals [OK]

Common Mistakes:

• Using FLOAT for money causing rounding errors
• Choosing too small precision or scale
• Confusing DECIMAL scale with precision