COPY command for bulk data loading in PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load data from a CSV file into the table.

PostgreSQL

COPY users FROM '[1]' DELIMITER ',' CSV;

Drag options to blanks, or click blank then click option'

A/path/to/file.csv

Busers.csv

Cdata.txt

D/data/users.csv

Attempts:

3 left

💡 Hint

Common Mistakes

Using a file name without a path when the file is not in the default directory.

Using a text file instead of a CSV file.

The COPY command requires the full path to the CSV file to load data correctly.

2fill in blank

medium

Complete the code to specify that the CSV file has a header row.

PostgreSQL

COPY products FROM '/data/products.csv' DELIMITER ',' CSV [1];

Drag options to blanks, or click blank then click option'

AWITH HEADER

BHEADER

CHEADERS

DFIRSTROW

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'WITH HEADER' which is invalid syntax.

Forgetting to specify HEADER when the CSV has column names.

The HEADER option tells PostgreSQL to skip the first row of the CSV file because it contains column names.

3fill in blank

hard

Fix the error in the COPY command to load data from a CSV file with tab delimiter.

PostgreSQL

COPY sales FROM '/data/sales.csv' DELIMITER [1] CSV;

Drag options to blanks, or click blank then click option'

A'\t'

B,

C'\n'

D';'

Attempts:

3 left

💡 Hint

Common Mistakes

Using a comma or semicolon instead of tab.

Not using quotes around the delimiter.

To specify a tab delimiter, use the escape sequence '\t' inside single quotes.

4fill in blank

hard

Fill both blanks to load data from a CSV file with semicolon delimiter and skip the header row.

PostgreSQL

COPY inventory FROM '/data/inventory.csv' DELIMITER [1] CSV [2];

Drag options to blanks, or click blank then click option'

A';'

BHEADER

CWITH HEADER

D','

Attempts:

3 left

💡 Hint

Common Mistakes

Using comma as delimiter instead of semicolon.

Using 'WITH HEADER' which is invalid syntax.

The delimiter for semicolon is ';' in quotes, and HEADER skips the first row.

5fill in blank

hard

Fill all three blanks to load data from a CSV file with pipe delimiter, skip header, and specify NULL values as empty strings.

PostgreSQL

COPY orders FROM '/data/orders.csv' DELIMITER [1] CSV [2] NULL [3];

Drag options to blanks, or click blank then click option'

A'|'

BHEADER

C''

D'NULL'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'NULL' as a string instead of empty string for NULL.

Forgetting to quote the delimiter character.

The pipe character '|' is the delimiter, HEADER skips the first row, and NULL '' treats empty strings as NULL values.

Practice

1. What is the main purpose of the COPY command in PostgreSQL?

easy

A. To delete data from a table

B. To create a new table in the database

C. To quickly load or export large amounts of data between a file and a table

D. To update existing rows in a table

Solution

1. Step 1: Understand the function of COPY

   The COPY command is designed to transfer data efficiently between a file and a PostgreSQL table.

2. Step 2: Compare with other commands

   Unlike CREATE, UPDATE, or DELETE, COPY focuses on bulk data loading or exporting, not modifying table structure or individual rows.

3. Final Answer:

   To quickly load or export large amounts of data between a file and a table -> Option C

4. Quick Check:

   COPY = bulk data transfer [OK]

Hint: COPY is for fast bulk data load/export, not table changes [OK]

Common Mistakes:

• Confusing COPY with CREATE TABLE
• Thinking COPY updates rows
• Assuming COPY deletes data

2. Which of the following is the correct syntax to copy data from a CSV file into a PostgreSQL table named employees?

easy

A. COPY employees TO '/path/to/file.csv' WITH CSV HEADER;

B. COPY employees FROM '/path/to/file.csv' WITH CSV HEADER;

C. COPY employees FROM '/path/to/file.csv' DELIMITER ';';

D. COPY employees FROM '/path/to/file.csv' FORMAT JSON;

Solution

1. Step 1: Identify direction of COPY

   To load data into a table, use COPY ... FROM. COPY employees FROM '/path/to/file.csv' WITH CSV HEADER; and C use FROM, B uses TO which exports data.

2. Step 2: Check format and options

   COPY employees FROM '/path/to/file.csv' WITH CSV HEADER; uses WITH CSV HEADER which is correct for CSV files with headers. COPY employees FROM '/path/to/file.csv' DELIMITER ';'; uses DELIMITER ';' but no CSV keyword, which is less clear. COPY employees FROM '/path/to/file.csv' FORMAT JSON; uses FORMAT JSON which is invalid for COPY.

3. Final Answer:

   COPY employees FROM '/path/to/file.csv' WITH CSV HEADER; -> Option B

4. Quick Check:

   Load CSV with header = COPY ... FROM ... WITH CSV HEADER [OK]

Hint: Use COPY ... FROM for loading, WITH CSV HEADER for CSV files [OK]

Common Mistakes:

• Using COPY ... TO instead of FROM to load data
• Missing WITH CSV HEADER for CSV files with headers
• Using wrong format like JSON in COPY

3. Given the table products(id INT, name TEXT, price NUMERIC), what will be the result of this command?

COPY products FROM '/tmp/products.csv' WITH CSV HEADER;

Assuming /tmp/products.csv contains:

id,name,price
1,Pen,1.20
2,Notebook,2.50
3,Eraser,0.80

medium

A. No rows inserted because HEADER skips all data

B. Error because price is numeric but CSV has strings

C. Only 2 rows inserted because of header misread

D. 3 rows inserted into products table

Solution

1. Step 1: Understand COPY with CSV HEADER

   The HEADER option tells COPY to skip the first line (column names) and load the rest as data rows.

2. Step 2: Check data types and rows

   The CSV data matches the table columns and types correctly: id as int, name as text, price as numeric. All 3 data rows will be inserted.

3. Final Answer:

   3 rows inserted into products table -> Option D

4. Quick Check:

   CSV HEADER skips first line, 3 data lines inserted [OK]

Hint: CSV HEADER skips first line; all data rows load if types match [OK]

Common Mistakes:

• Thinking HEADER skips all rows
• Assuming numeric columns reject string input
• Confusing COPY direction or syntax

4. You run this command:

COPY customers FROM '/data/customers.csv' WITH CSV;

But get an error: ERROR: could not open file "/data/customers.csv": Permission denied
What is the most likely cause?

medium

A. The PostgreSQL server process lacks permission to read the file

B. The CSV file format is incorrect

C. The COPY command syntax is wrong

D. The customers table does not exist

Solution

1. Step 1: Analyze the error message

   The error says "Permission denied" when opening the file, indicating a file access issue.

2. Step 2: Understand file permissions in COPY

   PostgreSQL server must have OS-level read permission on the file. If it lacks permission, this error occurs.

3. Final Answer:

   The PostgreSQL server process lacks permission to read the file -> Option A

4. Quick Check:

   Permission denied = file access issue [OK]

Hint: Permission denied means PostgreSQL can't read the file [OK]

Common Mistakes:

• Assuming syntax error causes permission denied
• Thinking CSV format causes file access error
• Ignoring file permissions on server

5. You want to load data from a CSV file into a table but skip rows where the age column is empty or NULL. Which approach using COPY and PostgreSQL features is best?

hard

A. Use COPY to load all data into a staging table, then insert filtered rows into the target table

B. Use COPY with WHERE clause to skip rows with empty age

C. Use COPY with an option to ignore NULL values in age column

D. Modify the CSV file manually to remove rows with empty age before COPY

Solution

1. Step 1: Understand COPY limitations

   COPY does not support filtering rows or WHERE clauses during import.

2. Step 2: Use staging table for filtering

   Load all data into a temporary or staging table, then run an INSERT INTO ... SELECT ... WHERE age IS NOT NULL to filter rows.

3. Step 3: Consider manual CSV editing

   While manual editing works, it is inefficient and error-prone for large files.

4. Final Answer:

   Use COPY to load all data into a staging table, then insert filtered rows into the target table -> Option A

5. Quick Check:

   COPY can't filter; use staging table + filter [OK]

Hint: COPY can't filter; load then filter with SQL [OK]

Common Mistakes:

• Expecting COPY to filter rows directly
• Looking for non-existent COPY options to ignore NULLs
• Relying on manual CSV edits for large data