error: relation "todo" does not exist

Node.js · updated 2026-11-10

Raised by Postgres (SQLSTATE 42P01) when a query names a table, view or sequence it cannot find in the search_path. node-postgres throws it with a position pointing at the name, psycopg raises UndefinedTable, and Django and SQLAlchemy wrap it as ProgrammingError. Typical after a deploy whose migrations did not run, or when the app points at a different database than you think.

error: relation "todo" does not exist
    at node_modules/pg/lib/client.js:694:17
    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
  code: '42P01', position: '15'

Quick fix

Compare the name in the error with the real table. Postgres lowercases unquoted names, so a table created as "Orders" (quoted) must be queried as "Orders", and select * from Orders looks for orders. If the name is right, the table is missing where you looked: the migration did not run on this database, the app is connected to another database, or the table lives in a schema outside the search_path.

1. Read the exact name in the error. Lowercased compared with your code means a quoting problem.
2. List what exists: \dt *.* in psql, or select table_schema, table_name from information_schema.tables.
3. Check the connection string the failing process uses (host, database name). Staging and production are often mixed up.
4. Run the migrations against that database (prisma migrate deploy, python manage.py migrate, alembic upgrade head, or your tool).
5. Table in another schema: qualify it (analytics.events) or add the schema to search_path.

Why it happens

Other fixes

• Through Supabase's API (supabase.from(...)) a missing table shows up as PostgREST error PGRST205, "Could not find the table ... in the schema cache", not as this message. Check the name, and reload the schema cache after creating the table outside a migration.
• In tests, create the schema before the first query (run migrations in the test setup).

Same error, other wording

• psycopg.errors.UndefinedTable: relation "todo" does not exist
• django.db.utils.ProgrammingError: relation "app_order" does not exist
• relation "orders" does not exist (table created as "Orders")

Related errors

• psycopg.errors.UndefinedColumn: column "titel" does not exist
• django.db.utils.OperationalError: no such table: orders_order
• PrismaClientInitializationError: Can't reach database server at `db.example.com:5432`

More in Databases

• PrismaClientKnownRequestError: Unique constraint failed on the fields: (`email`)Node.js
• MongoServerError: E11000 duplicate key error collection: app.users index: email_1 dup...Node.js
• [ioredis] Unhandled error event: Error: connect ECONNREFUSED 127.0.0.1:6379Node.js
• psycopg2.OperationalError: server closed the connection unexpectedlyPython
• psycopg.errors.UniqueViolation: duplicate key value violates unique constraint...Python
• error: new row violates row-level security policy for table "todos"Node.js
• error: infinite recursion detected in policy for relation "members"Node.js
• error: permission denied for table profilesNode.js
• error: null value in column "total" of relation "orders" violates not-null constraintNode.js
• error: insert or update on table "orders" violates foreign key constraint...Node.js
• error: invalid input syntax for type uuid: "undefined"Node.js
• sqlalchemy.exc.PendingRollbackError: This Session's transaction has been rolled back due...Python
• sqlite3.OperationalError: database is lockedPython
• pymongo.errors.ServerSelectionTimeoutError: localhost:27017: [Errno 111] Connection...Python
• redis.exceptions.ConnectionError: Error 111 connecting to localhost:6379. Connection...Python

References: PostgreSQL docs: identifiers and case folding, PostgreSQL docs: schema search path, PostgREST docs: error codes (42P01 and PGRST205)

Spotted a mistake? Email hello@greatwork.company. About Runheed.