How to fix ERROR: value too long for type character varying(n) in PostgreSQL

The error message from PostgreSQL may not always clearly indicate which column rejected the value. Check your application logs to see which INSERT or UPDATE operation failed, then identify the column being populated. You can also examine your table definition:

\d table_name

This shows all columns and their VARCHAR length constraints.

If the data legitimately needs to be longer, alter the table to increase the VARCHAR limit:

ALTER TABLE users ALTER COLUMN email TYPE varchar(255);

This approach preserves all data and accommodates longer values. There is no performance penalty in PostgreSQL for increasing VARCHAR length limits compared to TEXT.

If you want to store only the first n characters and discard the rest, use explicit casting in your INSERT/UPDATE:

INSERT INTO users (email) VALUES ('[email protected]'::varchar(50));

This truncates to 50 characters without raising an error. Only use this if losing data is acceptable.

If you need to store strings of variable length without constraints, change the column type to TEXT:

ALTER TABLE users ALTER COLUMN description TYPE text;

PostgreSQL TEXT and VARCHAR (without length) have identical performance and no practical limit (up to ~1GB per value). This is often the best choice when length requirements are uncertain.

Add validation in your application code to check string lengths before attempting database operations. This prevents round-trips to the database and provides better user feedback:

if (email.length > 100) {
  throw new Error('Email must be 100 characters or less');
}