Why PostgreSQL advanced features matter - See It in Action

Why PostgreSQL Advanced Features Matter

📖 Scenario: You are working for a small online bookstore. You want to organize your book data efficiently and use some advanced PostgreSQL features to make your database smarter and faster.

🎯 Goal: Build a simple PostgreSQL database table for books, add a configuration for a price threshold, write a query to filter books by price above the threshold, and complete the setup with an index to speed up queries.

📋 What You'll Learn

Create a table named books with columns id (integer), title (text), and price (numeric).

Add a variable price_limit to set a price threshold.

Write a query to select books priced above price_limit (20).

Create an index on the price column to optimize queries.

💡 Why This Matters

🌍 Real World

Online stores and businesses use PostgreSQL advanced features to handle large data efficiently and make queries faster.

💼 Career

Database administrators and backend developers use these features to optimize database performance and write smarter queries.

1

Create the books table

Write a SQL statement to create a table called books with columns id as integer, title as text, and price as numeric.

PostgreSQL

-- Your code here

Hint

Use CREATE TABLE followed by the table name and define each column with its data type.

2

Set a price threshold variable

Declare a variable called price_limit and set it to 20. Use the DO block with DECLARE to define this variable in PostgreSQL.

PostgreSQL

CREATE TABLE books (
    id INTEGER,
    title TEXT,
    price NUMERIC
);

-- Your code here

Hint

Use a DO block with DECLARE to create variables in PostgreSQL procedural code.

3

Query books priced above the threshold

Write a SQL query that selects title and price from books where the price is greater than 20 (the price_limit).

PostgreSQL

CREATE TABLE books (
    id INTEGER,
    title TEXT,
    price NUMERIC
);

DO $$
DECLARE
    price_limit NUMERIC := 20;
BEGIN
    NULL; -- placeholder
END $$;

-- Your code here

Hint

Use a simple SELECT with a WHERE clause to filter books by price. For advanced features, you can also explore FILTER or window functions later.

4

Create an index on the price column

Write a SQL statement to create an index named idx_price on the price column of the books table to speed up price queries.

PostgreSQL

CREATE TABLE books (
    id INTEGER,
    title TEXT,
    price NUMERIC
);

DO $$
DECLARE
    price_limit NUMERIC := 20;
BEGIN
    NULL; -- placeholder
END $$;

SELECT title, price
FROM books
WHERE price > 20;

-- Your code here

Hint

Use CREATE INDEX followed by the index name and the table and column to index.

Practice

1. Which of the following is a key advantage of PostgreSQL's advanced features?

easy

A. They allow storing complex data types like JSON and arrays.

B. They make the database only work with simple text data.

C. They remove the need for any indexes.

D. They prevent any data from being updated.

Solution

1. Step 1: Understand PostgreSQL advanced features

   PostgreSQL supports complex data types such as JSON, arrays, and custom types, which allow flexible data storage.

2. Step 2: Compare options with this knowledge

   They allow storing complex data types like JSON and arrays. correctly states this advantage, while others describe incorrect or impossible behaviors.

3. Final Answer:

   They allow storing complex data types like JSON and arrays. -> Option A

4. Quick Check:

   Advanced features = complex data support [OK]

Hint: Remember: PostgreSQL handles complex data types easily [OK]

Common Mistakes:

• Thinking PostgreSQL only supports simple text
• Believing indexes are not needed
• Assuming data cannot be updated

2. Which of the following is the correct syntax to create a table with a JSONB column in PostgreSQL?

easy

A. CREATE TABLE data (info JSONB);

B. CREATE TABLE data (info JSON);

C. CREATE TABLE data (info TEXT[]);

D. CREATE TABLE data (info BLOB);

Solution

1. Step 1: Recall JSONB column syntax in PostgreSQL

   PostgreSQL uses JSONB as a binary JSON storage type, declared as JSONB in table definitions.

2. Step 2: Check each option

   CREATE TABLE data (info JSONB); uses JSONB correctly. CREATE TABLE data (info JSON); uses JSON (also valid but not JSONB). CREATE TABLE data (info TEXT[]); uses TEXT array, not JSONB. CREATE TABLE data (info BLOB); uses BLOB which is not PostgreSQL syntax.

3. Final Answer:

   CREATE TABLE data (info JSONB); -> Option A

4. Quick Check:

   JSONB column syntax = CREATE TABLE ... (info JSONB) [OK]

Hint: Use JSONB for efficient JSON storage in PostgreSQL [OK]

Common Mistakes:

• Confusing JSON and JSONB types
• Using TEXT[] instead of JSONB
• Using BLOB which is not PostgreSQL type

3. Given the table users(id SERIAL PRIMARY KEY, data JSONB) with data:
{"name": "Alice", "age": 30} in the data column, what does this query return?

SELECT data->>'name' FROM users WHERE data->>'age' = '30';

medium

A. Returns all data rows regardless of age.

B. Returns the age 30 as a number.

C. Returns the name 'Alice' for users aged 30.

D. Returns an error due to wrong JSON syntax.

Solution

1. Step 1: Understand JSONB operators in the query

   The operator ->> extracts JSON object field as text. The WHERE clause filters rows where age equals '30' as text.

2. Step 2: Analyze query result

   The SELECT returns the 'name' field as text for rows matching age '30'. So it returns 'Alice'.

3. Final Answer:

   Returns the name 'Alice' for users aged 30. -> Option C

4. Quick Check:

   data->>'name' with age filter = 'Alice' [OK]

Hint: ->> extracts text from JSONB fields [OK]

Common Mistakes:

• Confusing -> and ->> operators
• Expecting numeric type instead of text
• Ignoring WHERE filter on JSONB field

4. Identify the error in this PostgreSQL query using JSONB:

SELECT data->'name' FROM users WHERE data->>'age' = 30;

medium

A. The JSONB column must be cast to text before querying.

B. The operator -> cannot be used in SELECT.

C. The query is correct and will run without errors.

D. The comparison value 30 should be a string '30'.

Solution

1. Step 1: Check WHERE clause comparison

   data->>'age' extracts text, so comparing to number 30 causes type mismatch.

2. Step 2: Correct the comparison

   Comparison should be to string '30' to match extracted text value.

3. Final Answer:

   The comparison value 30 should be a string '30'. -> Option D

4. Quick Check:

   Compare JSON text with string '30' [OK]

Hint: Compare JSON text fields with strings, not numbers [OK]

Common Mistakes:

• Using numeric 30 instead of string '30'
• Thinking -> operator is invalid in SELECT
• Trying to cast JSONB unnecessarily

5. You want to store user preferences as key-value pairs and query them efficiently. Which PostgreSQL feature best supports this need?

hard

A. Storing preferences in separate tables without indexes.

B. Using JSONB columns with GIN indexes.

C. Using arrays of text without indexes.

D. Storing preferences as plain text in VARCHAR columns.

Solution

1. Step 1: Identify data storage needs

   User preferences as key-value pairs fit well into JSONB columns for flexible schema.

2. Step 2: Consider query efficiency

   GIN indexes on JSONB columns speed up key-value queries efficiently.

3. Step 3: Evaluate other options

   Plain text or arrays lack flexibility and indexing; separate tables without indexes are slow.

4. Final Answer:

   Using JSONB columns with GIN indexes. -> Option B

5. Quick Check:

   JSONB + GIN index = fast key-value queries [OK]

Hint: Use JSONB with GIN index for fast key-value queries [OK]

Common Mistakes:

• Ignoring indexing for JSONB queries
• Using plain text which is inflexible
• Not using JSONB for key-value data