SELECT with PostgreSQL-specific features

Introduction

The SELECT statement lets you get data from a database. PostgreSQL adds special features to make selecting data easier and more powerful.

When you want to get data with extra options like limiting rows or skipping some.

When you want to get data with special functions only in PostgreSQL.

When you want to sort data in a flexible way.

When you want to get unique rows or count rows easily.

When you want to combine results from multiple queries.

Syntax

PostgreSQL

SELECT [DISTINCT | ALL] column1, column2, ...
FROM table_name
[WHERE condition]
[ORDER BY column [ASC|DESC], ...]
[LIMIT number]
[OFFSET number]
[FETCH {FIRST | NEXT} [number] {ROW | ROWS} ONLY];

DISTINCT removes duplicate rows.

LIMIT and OFFSET help control how many rows you get and where to start.

Examples

Get unique cities from the customers table.

PostgreSQL

SELECT DISTINCT city FROM customers;

Get the 5 most recent orders.

PostgreSQL

SELECT * FROM orders ORDER BY order_date DESC LIMIT 5;

Skip first 10 expensive products and get next 5.

PostgreSQL

SELECT name, price FROM products WHERE price > 100 OFFSET 10 LIMIT 5;

Count how many employees are in the table.

PostgreSQL

SELECT COUNT(*) FROM employees;

Sample Program

This example creates a fruits table, adds some fruits, then shows how to get unique fruit names and how to get a few fruits sorted by color.

PostgreSQL

CREATE TABLE fruits (id SERIAL PRIMARY KEY, name TEXT, color TEXT);

INSERT INTO fruits (name, color) VALUES
('Apple', 'Red'),
('Banana', 'Yellow'),
('Grape', 'Purple'),
('Apple', 'Green'),
('Banana', 'Yellow');

SELECT DISTINCT name FROM fruits ORDER BY name ASC;

SELECT name, color FROM fruits ORDER BY color DESC LIMIT 3 OFFSET 1;

Important Notes

PostgreSQL supports many special functions you can use inside SELECT, like string or date functions.

Use LIMIT with OFFSET to paginate results, like pages in a book.

ORDER BY can sort by multiple columns, each ascending or descending.

Summary

SELECT gets data from tables with many options.

PostgreSQL adds features like DISTINCT, LIMIT, OFFSET, and ORDER BY for flexible queries.

Use these features to get exactly the data you want, in the order and amount you need.

Practice

1. What does the LIMIT clause do in a PostgreSQL SELECT query?

easy

A. It combines rows from two tables.

B. It restricts the number of rows returned by the query.

C. It removes duplicate rows from the result.

D. It sorts the rows in ascending order.

Solution

1. Step 1: Understand the purpose of LIMIT

   The LIMIT clause is used to specify the maximum number of rows to return from a query result.

2. Step 2: Compare with other options

   Sorting is done by ORDER BY, removing duplicates by DISTINCT, and combining tables by JOIN, so these are not correct.

3. Final Answer:

   It restricts the number of rows returned by the query. -> Option B

4. Quick Check:

   LIMIT = restrict rows [OK]

Hint: LIMIT caps rows returned, like a page size [OK]

Common Mistakes:

• Confusing LIMIT with ORDER BY
• Thinking LIMIT removes duplicates
• Mixing LIMIT with JOIN functionality

2. Which of the following is the correct syntax to select distinct city names from a table called customers?

easy

A. SELECT city FROM DISTINCT customers;

B. SELECT city DISTINCT FROM customers;

C. SELECT DISTINCT city FROM customers;

D. SELECT city FROM customers DISTINCT;

Solution

1. Step 1: Recall correct DISTINCT syntax

   In PostgreSQL, DISTINCT comes immediately after SELECT and before the column list.

2. Step 2: Validate each option

   SELECT DISTINCT city FROM customers; correctly places DISTINCT after SELECT. Options A, B, and D misuse DISTINCT placement causing syntax errors.

3. Final Answer:

   SELECT DISTINCT city FROM customers; -> Option C

4. Quick Check:

   SELECT DISTINCT = correct syntax [OK]

Hint: DISTINCT always follows SELECT keyword [OK]

Common Mistakes:

• Placing DISTINCT after column names
• Using DISTINCT after FROM clause
• Misordering keywords causing syntax errors

3. Given the table products with columns id, name, and price, what will this query return?

SELECT name FROM products ORDER BY price DESC LIMIT 2;

medium

A. The two products with the lowest prices.

B. An error because LIMIT cannot be used with ORDER BY.

C. All products sorted by price descending.

D. The two products with the highest prices.

Solution

1. Step 1: Understand ORDER BY with DESC

   ORDER BY price DESC sorts products from highest to lowest price.

2. Step 2: Apply LIMIT 2

   LIMIT 2 restricts the output to only the first two rows after sorting, so the two most expensive products.

3. Final Answer:

   The two products with the highest prices. -> Option D

4. Quick Check:

   ORDER BY DESC + LIMIT = top rows [OK]

Hint: ORDER BY DESC + LIMIT picks top items [OK]

Common Mistakes:

• Thinking LIMIT returns lowest prices
• Believing LIMIT causes syntax error with ORDER BY
• Ignoring DESC means descending order

4. Identify the error in this PostgreSQL query:

SELECT DISTINCT name, price FROM products LIMIT;

medium

A. LIMIT requires a number to specify how many rows to return.

B. DISTINCT cannot be used with multiple columns.

C. SELECT must include WHERE clause when using LIMIT.

D. The table name is missing.

Solution

1. Step 1: Check LIMIT usage

   LIMIT must be followed by a number indicating how many rows to return; here it is missing.

2. Step 2: Validate other parts

   DISTINCT can be used with multiple columns, WHERE is optional, and table name is present as products.

3. Final Answer:

   LIMIT requires a number to specify how many rows to return. -> Option A

4. Quick Check:

   LIMIT needs a number [OK]

Hint: Always put a number after LIMIT [OK]

Common Mistakes:

• Omitting number after LIMIT
• Thinking DISTINCT can't use multiple columns
• Assuming WHERE is mandatory with LIMIT

5. You want to get the third and fourth highest salaries from the employees table with column salary. Which query correctly achieves this in PostgreSQL?

hard

A. SELECT salary FROM employees ORDER BY salary DESC LIMIT 2 OFFSET 2;

B. SELECT salary FROM employees ORDER BY salary ASC LIMIT 2 OFFSET 3;

C. SELECT DISTINCT salary FROM employees LIMIT 2 OFFSET 3 ORDER BY salary DESC;

D. SELECT salary FROM employees LIMIT 2 OFFSET 2 ORDER BY salary DESC;

Solution

1. Step 1: Understand OFFSET and LIMIT

   OFFSET 2 skips the first two highest salaries, LIMIT 2 returns the next two rows.

2. Step 2: Check ORDER BY direction

   ORDER BY salary DESC sorts salaries from highest to lowest, so OFFSET 2 skips top two highest.

3. Step 3: Validate options

   SELECT salary FROM employees ORDER BY salary DESC LIMIT 2 OFFSET 2; correctly orders DESC, uses LIMIT 2 and OFFSET 2. SELECT salary FROM employees ORDER BY salary ASC LIMIT 2 OFFSET 3; orders ASC (wrong direction), C misplaces ORDER BY, D places ORDER BY after LIMIT (syntax error).

4. Final Answer:

   SELECT salary FROM employees ORDER BY salary DESC LIMIT 2 OFFSET 2; -> Option A

5. Quick Check:

   OFFSET skips rows, LIMIT picks next [OK]

Hint: Use OFFSET to skip, LIMIT to pick rows [OK]

Common Mistakes:

• Using ASC instead of DESC for highest values
• Placing ORDER BY after LIMIT
• Confusing OFFSET number with row count