© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•3mo ago•
28 replies
Mohamed

PostgREST Issues

PostgREST
PostgREST returns "relation 'users' does not exist" (42P01) for UPDATE operations even though the table exists in public schema, all permissions are granted (anon/authenticated/service_role), schema USAGE is granted, RLS is enabled with policies, and SELECT operations work fine. I've verified the table exists, confirmed permissions with has_table_privilege(), added .schema('public') to queries, tried NOTIFY pgrst commands (didn't work), and even using secret key still fails. Is this a PostgREST schema cache issue that requires PostgREST to be restarted to refresh the cache? If so, how do I request this? I've created RPC functions as a workaround that work (bypass PostgREST), but I'd like to fix the root cause.
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

PostgREST
SupabaseSSupabase / help-and-questions
6mo ago
PostgREST refresh
SupabaseSSupabase / help-and-questions
3mo ago
Configure PostgREST RBAC
SupabaseSSupabase / help-and-questions
2mo ago
Auth and postgrest unhealthy
SupabaseSSupabase / help-and-questions
3mo ago