Supabase Error PGRST205: Table Not Found in Schema Cache

Supabase error PGRST205 (Table Not Found in Schema Cache) explained: what it means, why it happens, and how to fix it — with copy-paste code examples.

Error code PGRST205 Supabase Last verified 2026-08-19

Quick Answer

Verify the exact table name with SELECT tablename FROM pg_tables WHERE schemaname='public'. If that does not apply, reload the schema cache: run NOTIFY pgrst, 'reload schema' or use supabase db push — the full checklist is below.

Error Code

Error code: PGRST205
Official name: Table Not Found in Schema Cache
Service: Supabase

What does this error mean?

Caused when the table specified in the URI is not found.

Common Causes

How to Fix

  1. Verify the exact table name with SELECT tablename FROM pg_tables WHERE schemaname='public'
  2. Reload the schema cache: run NOTIFY pgrst, 'reload schema' or use supabase db push
  3. Confirm the table lives in the exposed schema (public by default)
  4. Remember the difference from PostgreSQL 42P01: PGRST205 is PostgREST's cache, 42P01 is the database

Code Examples

Reload the PostgREST schema cache sql 
-- in the SQL editor / psql, after creating or altering tables:
NOTIFY pgrst, 'reload schema';

This forces PostgREST to rebuild its schema cache so newly created tables resolve immediately.

Framework-Specific Fixes

supabase-cli

After creating tables locally, run supabase db push and restart local dev so PostgREST rebuilds its cache.

supabase db push
supabase start

You Might Also Like

PGRST116 Multiple or Zero Rows for a Singular Request More than 1 or no items were returned when requesting a singular response. PGRST203 Ambiguous Function Overload Caused by requesting overloaded functions with the same argument names but different types, or by using a… PostgreSQL42P01 Undefined Table The referenced table does not exist in the current schema search path. MySQL1146 Table Doesn't Exist Table '%s.%s' doesn't exist

Frequently Asked Questions

Why am I seeing Supabase error PGRST205?

Most often this happens when table name typo in .from('tabe'), or when table created in the database but the PostgREST schema cache was not reloaded.

How do I fix Supabase error PGRST205?

Verify the exact table name with SELECT tablename FROM pg_tables WHERE schemaname='public'.

Which frameworks have documented fixes for error PGRST205?

This page documents fixes for: supabase-cli.

Official Sources

This page is based on the official Supabase documentation linked below and adds practical troubleshooting guidance on top.