What causes "relation 'table_name' does not exist"?

Table exists in a different schema (not in current search_path) Case sensitivity mismatch - table created with quotes (CREATE TABLE "MyTable") but referenced without exact casing Table name misspelled or typo in the SQL query

Is the "relation 'table_name' does not exist" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

How to fix relation 'table_name' does not exist in PostgreSQL

PostgreSQLINTERMEDIATEMEDIUMUpdated Dec 25, 2025· 264 views

This error occurs when PostgreSQL cannot find a table, view, or other relation with the specified name. It's usually caused by schema issues, case sensitivity problems, typos, or incorrect database connections. Fix by verifying the table exists, checking exact naming and case, specifying the correct schema, or adjusting search_path settings.

Quick fix

Fixes relation 'table_name' does not exist

\dt

Verify the table exists
Check the exact table name and case sensitivity
Specify the correct schema
Verify database connection

postgresql — error

$\dt
relation 'table_name' does not exist

What this error means

In PostgreSQL, a 'relation' refers to any database object like tables, views, sequences, or indexes. When you get this error, it means PostgreSQL looked for the specified relation in the current search path (typically the public schema) but couldn't find it. The database doesn't see the table you're trying to query, which could happen for several reasons including the table existing in a different schema, case sensitivity issues, or the table simply not existing.

Typical symptoms

SQL queries fail immediately with the exact error message
Error appears only for specific tables while others work fine
Queries work in some connections but not others
The table exists in the database but queries still fail
Case-sensitive errors when table name has uppercase letters

Common causes

Table exists in a different schema (not in current search_path)
Case sensitivity mismatch - table created with quotes (CREATE TABLE "MyTable") but referenced without exact casing
Table name misspelled or typo in the SQL query
Table was never created or was dropped accidentally
Connected to wrong database or wrong PostgreSQL instance
Insufficient user permissions to access the table
Schema search_path not configured correctly for custom schemas

How to fix "relation 'table_name' does not exist"

1Verify the table exists

Use the psql command line tool or query the information schema to check if the table exists:

bash

\dt

Or use this SQL query:

sql

SELECT table_name FROM information_schema.tables WHERE table_schema = 'public';

If your table is in a different schema, modify the query:

sql

SELECT table_name FROM information_schema.tables WHERE table_schema = 'your_schema_name';

2Check the exact table name and case sensitivity

PostgreSQL is case-insensitive for unquoted identifiers but case-sensitive for quoted identifiers. If the table name contains uppercase letters, you may need to quote it:

sql

-- If table was created without quotes (case-insensitive)
SELECT * FROM users;  -- works
SELECT * FROM USERS;  -- also works

-- If table was created WITH quotes (case-sensitive)
SELECT * FROM "MyTable";  -- must use exact casing
SELECT * FROM "mytable";  -- fails

Find the exact table name in your schema:

sql

SELECT schemaname, tablename FROM pg_tables WHERE tablename ILIKE 'your_table_name';

3Specify the correct schema

If the table exists in a schema other than "public", reference it with the schema name:

sql

-- Incorrect (looks in public schema by default)
SELECT * FROM orders;

-- Correct (if orders is in app_schema)
SELECT * FROM app_schema.orders;

Alternatively, set the search_path for your session:

sql

SET search_path TO app_schema, public;
SELECT * FROM orders;  -- now works

Or permanently set it in your connection:

sql

ALTER ROLE your_user SET search_path TO app_schema, public;

4Verify database connection

Ensure you're connected to the correct database:

bash

# Check current database
\c

# Connect to correct database
psql -U username -d correct_database_name -h localhost

If using an application connection string, verify:
- Host is correct
- Port is correct (default is 5432)
- Database name matches where the table was created
- Username has access to that database

5Check user permissions

Verify that your database user has the necessary permissions to access the table:

sql

-- View permissions
\dp table_name

-- Grant SELECT permission
GRANT SELECT ON table_name TO your_user;

-- Grant all permissions
GRANT ALL PRIVILEGES ON table_name TO your_user;

If the table is in a non-public schema, also ensure you have USAGE permission on the schema:

sql

GRANT USAGE ON SCHEMA schema_name TO your_user;

6Best practice - use consistent naming

To avoid this error in the future:

Recommended approach:
- Always use lowercase, unquoted table names: CREATE TABLE users (...)
- This makes PostgreSQL fold all references to lowercase automatically
- Use underscores for multi-word names: user_profiles, product_orders

sql

-- Good: simple, unambiguous
CREATE TABLE users (
  id SERIAL PRIMARY KEY,
  email VARCHAR(255)
);

SELECT * FROM users;  -- always works
SELECT * FROM USERS;  -- also works

-- Avoid: quoted names create case sensitivity
CREATE TABLE "Users" (...);  -- creates case-sensitive table
SELECT * FROM "Users";  -- must use exact casing

Advanced notes

In PostgreSQL, the default search_path is typically '"$user", public'. This means PostgreSQL first looks for objects in a schema matching your username, then in the public schema. When working with ORM tools (Prisma, SQLAlchemy, etc.), schema visibility depends on the connection string configuration. Some tools allow you to specify an initial schema - if this is set incorrectly, you may get this error even if the table exists in a different schema. For Prisma, use the schema parameter in the connection string: postgresql://user:password@localhost/db?schema=myschema. When using views instead of tables, the same error applies if the view doesn't exist or isn't in your search path.

Frequently asked questions

What does "relation 'table_name' does not exist" mean?: In PostgreSQL, a 'relation' refers to any database object like tables, views, sequences, or indexes. When you get this error, it means PostgreSQL looked for the specified relation in the current search path (typically the public schema) but couldn't find it. The database doesn't see the table you're trying to query, which could happen for several reasons including the table existing in a different schema, case sensitivity issues, or the table simply not existing.
How do I fix "relation 'table_name' does not exist"?: This error occurs when PostgreSQL cannot find a table, view, or other relation with the specified name. It's usually caused by schema issues, case sensitivity problems, typos, or incorrect database connections. Fix by verifying the table exists, checking exact naming and case, specifying the correct schema, or adjusting search_path settings.
What causes "relation 'table_name' does not exist"?: Table exists in a different schema (not in current search_path) Case sensitivity mismatch - table created with quotes (CREATE TABLE "MyTable") but referenced without exact casing Table name misspelled or typo in the SQL query
Is the "relation 'table_name' does not exist" error serious?: It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.