Character types (char, varchar, text) in PostgreSQL - Step-by-Step Execution

Concept Flow - Character types (char, varchar, text)

Start: Define column type

↓

Choose char(n)

↓

Choose varchar(n)

↓

Choose text

↓

Store data accordingly

↓

Retrieve data

↓

Trim spaces for char(n) if needed

↓

End

The flow shows choosing between char, varchar, and text types, storing data, and how data is handled on retrieval.

Execution Sample

PostgreSQL

CREATE TABLE example (
  fixed_char CHAR(5),
  var_char VARCHAR(5),
  long_text TEXT
);

INSERT INTO example VALUES ('abc', 'abc', 'abc');
SELECT * FROM example;

Creates a table with char, varchar, and text columns, inserts 'abc' into each, then selects all rows.

Execution Table

Step	Action	Input Value	Stored Value	Notes
1	Create table with CHAR(5), VARCHAR(5), TEXT columns	N/A	Table schema created	Defines column types
2	Insert 'abc' into CHAR(5)	'abc'	'abc '	CHAR pads with spaces to length 5
3	Insert 'abc' into VARCHAR(5)	'abc'	'abc'	VARCHAR stores exact length up to 5
4	Insert 'abc' into TEXT	'abc'	'abc'	TEXT stores exact length, no limit here
5	Select all rows	N/A	'abc ', 'abc', 'abc'	Retrieves stored values
6	Trim CHAR(5) value on retrieval if needed	'abc '	'abc'	Spaces can be trimmed for display
7	End	N/A	N/A	Execution complete

💡 All values inserted and retrieved according to their type rules

Variable Tracker

Variable	Start	After Insert	After Select	Final
fixed_char	NULL	'abc '	'abc '	'abc' (trimmed for display)
var_char	NULL	'abc'	'abc'	'abc'
long_text	NULL	'abc'	'abc'	'abc'

Key Moments - 3 Insights

Why does CHAR(5) store 'abc' as 'abc ' with spaces?

CHAR(n) always stores exactly n characters, padding with spaces if input is shorter, as shown in execution_table step 2.

Does VARCHAR(5) pad spaces like CHAR(5)?

No, VARCHAR stores only the input length up to the max, no padding, as seen in step 3.

Is there a length limit for TEXT type?

TEXT has no practical length limit in PostgreSQL, it stores the full input as is, shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the stored value for CHAR(5) after inserting 'abc'?

A 'abc '

B 'abc'

C 'abc '

D 'abc\0\0'

💡 Hint

Check execution_table row 2 under Stored Value column

At which step does VARCHAR(5) store the exact input length without padding?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Look at execution_table row 3 for VARCHAR behavior

If you insert 'abcdef' into VARCHAR(5), what happens?

A Stores 'abcdef' fully

B Stores 'abcde' truncated

C Insertion fails due to length limit

D Stores 'abc ' padded

💡 Hint

VARCHAR(5) max length is 5, check PostgreSQL behavior for exceeding length

Concept Snapshot

Character types in PostgreSQL:
- CHAR(n): fixed length, pads spaces if shorter
- VARCHAR(n): variable length, max n characters, no padding
- TEXT: variable length, unlimited size
Use CHAR for fixed size, VARCHAR for limited variable size, TEXT for large text data.

Full Transcript

This visual execution shows how PostgreSQL stores and retrieves data using character types CHAR, VARCHAR, and TEXT. CHAR(n) always stores fixed length by padding spaces if input is shorter. VARCHAR(n) stores variable length strings up to n characters without padding. TEXT stores variable length strings with no practical limit. The example creates a table with these types, inserts 'abc' into each, and selects the data. The CHAR column stores 'abc' padded with two spaces to length 5, VARCHAR stores 'abc' exactly, and TEXT stores 'abc' exactly. On retrieval, CHAR values can be trimmed for display. This helps beginners understand how these types behave differently in storage and retrieval.

Practice

1. Which PostgreSQL character type stores text with a fixed length, padding with spaces if the input is shorter?

easy

A. CHAR(n)

B. VARCHAR(n)

C. TEXT

D. INT

Solution

1. Step 1: Understand fixed-length storage

   CHAR(n) stores exactly n characters, padding with spaces if input is shorter.

2. Step 2: Compare with other types

   VARCHAR(n) stores variable length up to n, TEXT has no limit, INT is numeric.

3. Final Answer:

   CHAR(n) -> Option A

4. Quick Check:

   Fixed length with padding = CHAR(n) [OK]

Hint: Fixed length with padding means CHAR(n) [OK]

Common Mistakes:

• Confusing VARCHAR(n) as fixed length
• Thinking TEXT has length limit
• Choosing numeric types by mistake

2. Which of the following is the correct syntax to declare a variable-length character column with a maximum of 50 characters in PostgreSQL?

easy

A. CHAR(50)

B. VARCHAR(50)

C. TEXT(50)

D. STRING(50)

Solution

1. Step 1: Identify variable-length syntax

   VARCHAR(n) declares variable-length text with max n characters.

2. Step 2: Check other options

   CHAR(50) is fixed length, TEXT has no length limit, STRING is invalid in PostgreSQL.

3. Final Answer:

   VARCHAR(50) -> Option B

4. Quick Check:

   Variable length with max limit = VARCHAR(n) [OK]

Hint: Use VARCHAR(n) for variable length with max size [OK]

Common Mistakes:

• Using TEXT with length limit (invalid)
• Confusing CHAR as variable length
• Using non-existent STRING type

3. Consider the following table and insert statements:

CREATE TABLE users (name CHAR(5));
INSERT INTO users VALUES ('Tom');
SELECT name, LENGTH(name) FROM users;

What will be the output of the SELECT query?

medium

A. name = 'Tom ', length = 5

B. name = 'Tom', length = 3

C. name = 'Tom', length = 5

D. name = 'Tom ', length = 3

Solution

1. Step 1: Understand CHAR(5) behavior on insert

   CHAR(5) pads 'Tom' with 2 spaces to make length 5.

2. Step 2: LENGTH function counts all characters including spaces

   LENGTH('Tom ') returns 5 because spaces count.

3. Final Answer:

   name = 'Tom ', length = 5 -> Option A

4. Quick Check:

   CHAR pads spaces, LENGTH counts them [OK]

Hint: CHAR pads spaces; LENGTH counts all characters [OK]

Common Mistakes:

• Assuming LENGTH ignores trailing spaces
• Thinking CHAR stores variable length
• Confusing CHAR with VARCHAR behavior

4. You have a table with a column defined as VARCHAR(10). You try to insert a string of 15 characters. What will happen?

medium

A. The string is truncated to 10 characters and inserted

B. The string is padded with spaces to 15 characters

C. An error is raised and insertion fails

D. The string is inserted fully ignoring the limit

Solution

1. Step 1: Understand VARCHAR(n) length limit enforcement

   VARCHAR(10) limits input to 10 characters strictly.

2. Step 2: Behavior on exceeding length

   PostgreSQL raises an error if input exceeds declared length.

3. Final Answer:

   An error is raised and insertion fails -> Option C

4. Quick Check:

   Exceeding VARCHAR limit causes error [OK]

Hint: Exceeding VARCHAR(n) length causes error, no truncation [OK]

Common Mistakes:

• Assuming automatic truncation happens
• Thinking VARCHAR pads with spaces
• Believing PostgreSQL ignores length limits

5. You want to store user comments of any length without worrying about size limits. Which PostgreSQL data type should you choose and why?

hard

A. INT, because it stores numeric values efficiently

B. CHAR(255), because it fixes length and saves space

C. VARCHAR(255), because it limits length to 255 characters

D. TEXT, because it stores variable-length text with no size limit

Solution

1. Step 1: Identify requirement for unlimited length

   User comments can be very long, so no fixed or limited length is suitable.

2. Step 2: Compare data types for length limits

   TEXT stores variable-length text with no size limit, unlike CHAR or VARCHAR.

3. Step 3: Exclude irrelevant types

   INT is numeric and unsuitable for text storage.

4. Final Answer:

   TEXT, because it stores variable-length text with no size limit -> Option D

5. Quick Check:

   No size limit needed = TEXT [OK]

Hint: Use TEXT for unlimited length text storage [OK]

Common Mistakes:

• Choosing CHAR or VARCHAR with fixed limits
• Confusing numeric types with text
• Assuming VARCHAR can store unlimited text