Troubleshooting Prepared Statement Errors with Supabase

When using Explo with Supabase, you may encounter errors such as:

prepared statement "S_XXX" does not exist

This typically occurs when connections are reset or reused. Explo relies on prepared statements, so if the pooler drops them, queries can fail unexpectedly.

Recommended Solutions

1. Use a Direct Connection: Connect Explo directly to your Supabase database. Direct connections maintain prepared statements for the session, eliminating “does not exist” errors.

2. Consider the Supabase Shared Pooler:

• As an alternative to direct connections, use Supabase’s shared/session pooler.

• This keeps sessions alive longer than the transaction pooler, reducing the chance of prepared statements being lost.

Summary

• Direct connection → Most reliable option.

• Shared pooler → Scales better than direct, but avoids transaction pooler issues.

• IPv4 → Must be enabled for Explo to connect successfully.