1
blocking issue
Source: supabase/supabase#43158 · opened by @rla675
Project ref: onrjgksbrzgvkemtnnyw
Persistent ERROR: 42P01 relation "public.comments" does not exist
• Table is visible in Table Editor (public schema)
• But SQL Editor: SELECT * FROM comments LIMIT 1; → 42P01 does not exist
• information_schema.tables query returns no 'comments'
• Tried: table delete/recreate multiple times, pg_notification_queue_usage() + NOTIFY reload schema (5+ times), project Restart (2 times), search_path TO public set
• RLS disabled, code uses public schema
• API (/rest/v1/comments) also 404 + same error
PostgREST schema cache or internal DB sync desync seems stuck. Please manually verify/re-sync the table or reset PostgREST cache.
Persistent ERROR: 42P01 relation "public.comments" does not exist
• Table is visible in Table Editor (public schema)
• But SQL Editor: SELECT * FROM comments LIMIT 1; → 42P01 does not exist
• information_schema.tables query returns no 'comments'
• Tried: table delete/recreate multiple times, pg_notification_queue_usage() + NOTIFY reload schema (5+ times), project Restart (2 times), search_path TO public set
• RLS disabled, code uses public schema
• API (/rest/v1/comments) also 404 + same error
PostgREST schema cache or internal DB sync desync seems stuck. Please manually verify/re-sync the table or reset PostgREST cache.
No pledges yet. Be the first to back this.
Comments
Similar requests
My main issue with Auth is the need to manually add a Trigger to create the profiles table
3 votes · 0 comments
Allow modifying SELECT RLS on public buckets
2 votes · 0 comments
URGENT – Pro plan not applied to active project, blocking access to support
1 vote · 0 comments
Intermittent "Unable to connect to server" Issue on Supabase (Free Plan)
1 vote · 0 comments
Error 502 with Supabase client when using Nginx as a reverse proxy
19 votes · 0 comments
No comments yet.