PostgreSQL Error 42601

SQLSTATE

42601

Condition name

syntax_error

Product

PostgreSQL

Versions

PostgreSQL 13 to 18 (examples run on PostgreSQL 18.6 in PGlite)

Category

Syntax & Names

Last reviewed

24 October 2026

What it means

SQLSTATE 42601 means PostgreSQL could not parse the statement: a word, symbol or the end of the text appeared where the grammar does not allow it, so nothing was run.

PostgreSQL parses the whole statement before running any of it. When the parser meets a token that cannot come next, it stops and reports that token: syntax error at or near "FROM" means the problem is at, or just before, the word FROM. psql adds a LINE line with a caret under that spot, and drivers return the same information as a character position. The real mistake is often one token earlier: a trailing comma before FROM, a missing comma between columns, an unclosed bracket. "syntax error at end of input" means the statement ended while the parser still expected more, such as a WHERE with no condition.

The most common source is SQL written for another database. SQL Server TOP and [brackets], MySQL backtick quoting and UPDATE ... LIMIT are not PostgreSQL syntax. Reserved words such as user, order and limit cannot be used as bare table or column names. A few checks that are not strictly grammar also use 42601, such as an INSERT whose column and value lists have different lengths, and UNION branches with different column counts. Because nothing ran, no data changed, but inside a transaction the error still aborts it (25P02).

Common causes

• A trailing comma before FROM or a closing bracket, or a missing comma between two columns.
• Syntax from another database: TOP n and [name] from SQL Server, `name` backticks and UPDATE or DELETE ... LIMIT from MySQL.
• A reserved word such as user, order, group or limit used as an unquoted table or column name.
• A string that contains an apostrophe (O'Brien) built into the SQL text without doubling the quote, which also opens the door to SQL injection.
• Double quotes used around a string value: "" is an empty identifier and "text" is a column name, not a string.
• A statement cut short or glued together by the application: an empty IN (), a dangling WHERE or AND, or a missing semicolon between two statements.
• Syntax that needs a newer PostgreSQL version than the server you are connected to.

Diagnose it

Read-only These queries only read the system catalogs (pg_catalog, information_schema) and statistics views such as pg_stat_activity and pg_locks. They do not change data, roles or settings, so they are safe to run first.

SELECT word, catcode, catdesc
FROM pg_get_keywords()
WHERE word IN ('user', 'order', 'limit', 'name')
ORDER BY word;

SELECT version();
SELECT current_setting('server_version_num') AS version_num;

EXPLAIN
SELECT id, name
FROM customers
ORDER BY name
LIMIT 5;

How to fix it

Each fix is labelled with what it changes. Try read-only checks and the least invasive fix first, and test changes outside production.

-- SQL Server: SELECT TOP 5 [name] FROM customers ORDER BY name;
SELECT "name" FROM customers ORDER BY name LIMIT 5;

-- the standard form also works
SELECT name FROM customers ORDER BY name FETCH FIRST 5 ROWS ONLY;

CREATE TABLE app_user (id int PRIMARY KEY, name text);

-- possible, but every query must then write "user"
CREATE TABLE "user" (id int PRIMARY KEY, name text);

-- hand-written SQL
SELECT * FROM customers WHERE name = 'O''Brien';

INSERT INTO customers (id, name, email)
VALUES (1, 'Sara', 'sara@example.com');

Examples

A trailing comma before FROM

The mistake is the comma after name, but PostgreSQL reports the next token, FROM, because a comma there could still have been followed by another column.

CREATE TABLE customers (id int, name text, email text);

SELECT id, name, FROM customers;

ERROR:  syntax error at or near "FROM"

SQL Server TOP in PostgreSQL

PostgreSQL reads TOP as a column name and then cannot place 5. The fix is SELECT * FROM customers LIMIT 5;. Square brackets fail the same way: SELECT [name] FROM customers gives syntax error at or near "[".

CREATE TABLE customers (id int, name text, email text);

SELECT TOP 5 * FROM customers;

ERROR:  syntax error at or near "5"

A reserved word as a table name

CREATE TABLE user (id int, name text);

ERROR:  syntax error at or near "user"

More values than columns in an INSERT

CREATE TABLE customers (id int, name text, email text);

INSERT INTO customers (id, name) VALUES (1, 'Sara', 'sara@example.com');

ERROR:  INSERT has more expressions than target columns

How to prevent it

Use parameters for every value from users or files, which avoids broken quoting and SQL injection together. Name tables and columns in lower case with underscores and avoid keywords, so nothing needs quoting. Format long statements one clause per line: the LINE number in the error then points straight at the clause.

When porting SQL from SQL Server or MySQL, test it against PostgreSQL (the PostgreSQL playground runs it in the browser) and use a formatter or linter that understands the PostgreSQL dialect. Check the server version before using syntax from the current documentation.

Common questions

Learn more on CodeWithSQL

• SQL syntax guide
• SQL Server to PostgreSQL
• MySQL to PostgreSQL

Official documentation

• PostgreSQL error codes (Appendix A)
• SQL syntax: lexical structure (identifiers, quoting, constants)
• SQL key words (Appendix C)
• SELECT (LIMIT and FETCH)

Last technically reviewed 24 October 2026; examples and diagnostics run on PostgreSQL 18.6 (PGlite 0.5.11). SQL-level examples were run in PGlite (PostgreSQL compiled to WebAssembly); examples that need a running server are shown as documented in the PostgreSQL documentation.