Why does putting the name in double quotes sometimes fix it and sometimes break it?

Double quotes preserve exact case and force PostgreSQL to match it letter-for-letter. Use quotes only if the object was created with quotes in the first place — quoting an all-lowercase name unquoted originally doesn't help, and can make the mismatch worse.

Can a table exist but PostgreSQL still say it doesn't?

Yes — if it's in a schema that isn't on your search_path, or you're connected to a different database than the one it was created in, PostgreSQL genuinely cannot see it, even though \dt would show it under the right connection.

Does a rolled-back transaction really cause this?

Yes. If a migration or script ran CREATE TABLE inside a transaction that later hit an error and rolled back, the table was never actually created, even if the CREATE TABLE statement itself reported success at the time it ran.

What's the fastest way to check if a table really exists?

Run \dt in psql, or query information_schema.tables — both reflect the committed state of whichever database you're currently connected to.

Fix "relation does not exist" in PostgreSQL: 6 Causes

sqlfmt▍

Fix "relation does not exist" in PostgreSQL: 6 Causes — sqlfmt

PostgreSQL's "relation does not exist" error is one of the most common messages developers hit, and it's rarely about a table that's actually missing. "Relation" is Postgres' umbrella term for tables, views, materialized views, sequences, and indexes — so the error can point at any of them. Here are the six causes that account for nearly every case, in the order you should check them.

Key takeaways

PostgreSQL folds unquoted identifiers to lowercase — MyTable and mytable are the same table, but "MyTable" in double quotes is not.
The default search_path is usually "$user", public — a table in another schema needs to be schema-qualified or added to the path.
A CREATE TABLE inside a transaction that later rolled back never persisted, even though the statement itself reported success at the time.
information_schema.tables and \dt in psql are the fastest ways to confirm what actually exists in the database you're connected to.

Cause 1: A misspelled or case-folded table name

PostgreSQL lowercases unquoted identifiers before matching them against the catalog. If a table was created with double quotes — which preserves its exact case — an unquoted reference to it will be folded to lowercase and won't match.

Case folding breaks an unquoted reference

-- Created with quotes, so the mixed case is preserved literally:
CREATE TABLE "UserAccounts" (id serial PRIMARY KEY);

-- Looks right, but fails:
SELECT * FROM UserAccounts;
-- ERROR:  relation "useraccounts" does not exist

-- Works, because it matches the quoted name exactly:
SELECT * FROM "UserAccounts";

Check and fix a schema mismatch

SHOW search_path;
-- "$user", public

-- Table lives in "analytics", not on the path:
SELECT * FROM orders;          -- relation "orders" does not exist
SELECT * FROM analytics.orders; -- works

How to Fix "relation does not exist" in PostgreSQL

Quick answer

FAQs

Does "relation" mean only tables?

Why does putting the name in double quotes sometimes fix it and sometimes break it?

Can a table exist but PostgreSQL still say it doesn't?

Does a rolled-back transaction really cause this?

What's the fastest way to check if a table really exists?

How to Fix MySQL Error 1146: Table Doesn't Exist

PostgreSQL “column does not exist”: Causes and Fixes

How to Fix “Conversion Failed When Converting” in SQL Server

Key takeaways

Cause 1: A misspelled or case-folded table name

Cause 2: The table lives in a different schema

Cause 3: You're connected to the wrong database

Cause 4: The CREATE TABLE was inside a transaction that rolled back

Cause 5: Referencing the table before it exists

How to fix it: a step-by-step checklist

Quick answer

FAQs

Does "relation" mean only tables?

Why does putting the name in double quotes sometimes fix it and sometimes break it?

Can a table exist but PostgreSQL still say it doesn't?

Does a rolled-back transaction really cause this?

What's the fastest way to check if a table really exists?

Keep reading

How to Fix MySQL Error 1146: Table Doesn't Exist

PostgreSQL “column does not exist”: Causes and Fixes

How to Fix “Conversion Failed When Converting” in SQL Server

Key takeaways

Cause 1: A misspelled or case-folded table name

Cause 2: The table lives in a different schema

Cause 3: You're connected to the wrong database

Cause 4: The CREATE TABLE was inside a transaction that rolled back

Cause 5: Referencing the table before it exists

How to fix it: a step-by-step checklist

Related PostgreSQL errors