Intermittent "relation does not exist" errors for tables that DO exist
We're experiencing intermittent relation "table_name" does not exist (error code 42P01) errors across multiple tables in our production database, despite the tables existing and being queryable.
We're using Drizzle ORM → Supavisor pooler (port 6543, transaction mode). I've attached an image of what our config looks like roughly.
We don't see these errors when we interface through the Supabase client but we do see the errors when we interface through Drizzle. Here's an example error log:
The tables do exist and usually the queries work but we've lately seen spikes in this error seemingly cyclically. Would love any thoughts on this from the community. Thanks!
We're using Drizzle ORM → Supavisor pooler (port 6543, transaction mode). I've attached an image of what our config looks like roughly.
We don't see these errors when we interface through the Supabase client but we do see the errors when we interface through Drizzle. Here's an example error log:
The tables do exist and usually the queries work but we've lately seen spikes in this error seemingly cyclically. Would love any thoughts on this from the community. Thanks!
