Subject: PostgREST schema cache broken: tables/views return PGRST205; RPC functions return PGRST202

Summary:
I'm experiencing an issue where PostgREST is returning PGRST205 ("Could not find table in schema cache") for tables that definitely exist in my public schema. I've tried restarting my project and triggering schema reload via select pg_notify('pgrst','reload schema'), but neither resolves it. This is breaking both my REST API access and Edge Functions.

What I've tried:

1. Verified tables exist in Postgres (to_regclass() returns non-null)
2. Checked exposed schemas include public in dashboard
3. Restarted project from dashboard
4. Ran select pg_notify('pgrst', 'reload schema');
5. Verified permissions: has_schema_privilege and has_table_privilege return true
6. Tried with both RLS enabled and disabled on different tables
7. Created test views - same issue
8. RPC functions also return PGRST202

Impact:

• Edge Functions using supabase-js are failing
• REST API endpoints returning PGRST205 for existing tables

Related issue found in community:
I found this thread where someone had PGRST202 errors with RPC functions. Their solution was:

1. Running NOTIFY pgrst, 'reload schema'
2. Granting permissions to all roles

But my situation differs:

1. I'm getting both PGRST205 (tables) and PGRST202 (functions)
2. I've already tried pg_notify('pgrst', 'reload schema') and project restarts
3. My permissions checks show everything should be correct (has_schema_privilege returns true)
4. Unlike that thread, my issue affects all existing tables, not just new functions

My question:
Has anyone experienced this? Are there other troubleshooting steps I should try before potentially needing to contact support? Could this be related to schema cache corruption?