Supabase session vs transaction pooler for a GUI
For a desktop database GUI that needs IPv4, start with Supabase’s session pooler. Transaction pooling is aimed at short-lived application requests. Choose the mode for the work you’re doing before troubleshooting the connection.
Match the endpoint to the job
- Desktop browsing and SQL sessions: use the session pooler when following Supabase's third-party-tool guidance.
- Serverless or edge application traffic: evaluate transaction pooling with a compatible driver configuration.
- Migrations and native backup tools: follow the provider's direct-connection guidance and verify network reachability.
These are the current recommendations in Supabase's connection guide. Copy the endpoint from the dashboard rather than guessing a hostname from the region.
Why the session matters
In session pooling, a client retains its underlying database connection for the session. In transaction pooling, the relationship is shorter-lived. Code or tools that assume persistent session state need to be evaluated accordingly. Supabase explains the mechanism in pooling and limits.
A useful desktop test is to connect, browse schemas, execute a bounded query, and then use the same connection for the next related task. Record any failure precisely rather than assuming all PostgreSQL endpoints are interchangeable.
Prepared statements require the right mode
Supabase documents prepared-statement support for direct and session connections, and restrictions for its transaction pooler. If a library uses automatic preparation, follow that library's documented setting. See the prepared-statement guidance. Do not apply a driver flag copied from another language to an unrelated GUI.
Name connections by what you use them for
Keep your everyday inspection connection clearly named and use a distinct configuration for administrative tools where needed. Document the mode as well as the project name. When a teammate reports a failure, compare mode, host, username, SSL settings and network reachability together.
plainDB's Supabase preset connects to PostgreSQL. It does not replace the Supabase dashboard for Auth, Storage, Realtime or Edge Functions administration. Select the client based on the database work you need, and keep the dashboard for the surrounding platform services.
Continue reading
Desktop workflow overview · Fix authentication
For the desktop workflow, compare plainDB features on Mac and Windows or download the 14-day trial.