Does SELECT * cause an ambiguous column name error?

Not by itself — SELECT * just expands to every column from every joined table, duplicates included, and most engines return both copies rather than erroring. The error shows up one step later, when you or a downstream query reference one of those duplicated column names by hand. Expand columns explicitly in joined production queries so duplicates never reach the result set in the first place.

Can an ambiguous column error happen in a single-table query?

Yes, in two situations: a CTE or subquery whose output columns collide with an outer query's table, or a PL/pgSQL function or stored procedure where a variable or parameter shares a name with a column. Both fix the same way as a join — qualify the reference or rename the colliding variable so only one name remains.

Why does the error point at a column instead of the join that caused it?

The engine resolves each column reference independently while binding the query, and it reports the ambiguity at the first unqualified reference it finds — typically in the SELECT list — rather than at the JOIN clause that introduced the second copy of the column. The join is the root cause; the column is just where the resolver gave up.

Does the USING clause work the same way in every SQL dialect?

PostgreSQL, MySQL, SQLite, and BigQuery all support USING(column) and collapse the joined column into a single, unambiguous output column. SQL Server's T-SQL has no USING clause at all, so an explicit ON with alias-qualified columns is the only option there.

Is 'ambiguous column name' a syntax error?

Not technically — most engines catch it during query binding and name resolution, a step that runs after parsing confirms the SQL is well-formed but before any rows are read. That's why the message names a specific column rather than a token position the way a true syntax error, like PostgreSQL's 'syntax error at or near', does.

SQL Errors

SQL "Ambiguous Column Name": Causes and Fixes

By Sharon Ben-Moshe · July 13, 2026 · 7 min read

Sharon Ben-Moshe is the founder of sqlfmt, a browser-based SQL formatter and validator with misspelled-keyword suggestions across PostgreSQL, MySQL, SQLite, SQL Server, and BigQuery.

A SQL "ambiguous column name" error means a JOIN produced same-named columns and your query didn't say which one it meant. Here's the fix, dialect by dialect.

Quick answer

The "ambiguous column name" error (Postgres: column reference "id" is ambiguous; MySQL: Column 'id' in field list is ambiguous; SQL Server: Msg 209) fires when a query joins two or more tables that share a column name and references that column without saying which table it comes from. Fix it by qualifying the column with its table name or alias, such as orders.id instead of id, or by using a USING(column) clause when the join key is named identically on both sides (not supported in SQL Server). It is a name-resolution error caught before the query runs, not a data problem.

SQL "Ambiguous Column Name": Causes and Fixes

Quick answer

FAQs

Does SELECT * cause an ambiguous column name error?

Can an ambiguous column error happen in a single-table query?

Why does the error point at a column instead of the join that caused it?

Does the USING clause work the same way in every SQL dialect?

Is 'ambiguous column name' a syntax error?

Fix BigQuery "Unrecognized Name" Error: Scoping and Syntax Rules

SQLite "Datatype Mismatch" (Error 20): Type Affinity and Strict Tables

PostgreSQL statement_timeout (Error 57014): Causes and Prevention

What actually causes an "ambiguous column name" error?

How do I fix "column reference ... is ambiguous" in PostgreSQL?

How do I fix "Column ... in field list is ambiguous" in MySQL?

How do I fix "Ambiguous column name" (Error 209) in SQL Server?

Does the same error show up in SQLite and BigQuery?

Does USING or NATURAL JOIN avoid the problem?

Checklist: catch ambiguous column errors before you hit run

Wrapping up

Quick answer

FAQs

Does SELECT * cause an ambiguous column name error?

Can an ambiguous column error happen in a single-table query?

Why does the error point at a column instead of the join that caused it?

Does the USING clause work the same way in every SQL dialect?

Is 'ambiguous column name' a syntax error?

Keep reading

Fix BigQuery "Unrecognized Name" Error: Scoping and Syntax Rules

SQLite "Datatype Mismatch" (Error 20): Type Affinity and Strict Tables

PostgreSQL statement_timeout (Error 57014): Causes and Prevention

What actually causes an "ambiguous column name" error?

How do I fix "column reference ... is ambiguous" in PostgreSQL?

How do I fix "Column ... in field list is ambiguous" in MySQL?

How do I fix "Ambiguous column name" (Error 209) in SQL Server?

Does the same error show up in SQLite and BigQuery?

Does USING or NATURAL JOIN avoid the problem?

Checklist: catch ambiguous column errors before you hit run

Wrapping up