PostgreSQL: Connection guide
Enter the PostgreSQL database name and role. Check schema permissions and TLS requirements. For Supabase, use the direct or pooler details provided by the project; IPv4/IPv6 reachability and pooler behavior can affect your workflow.
PostgreSQL: Connection guide
Query, explore and develop with Oracle, PostgreSQL, MySQL, MariaDB, SQLite and Microsoft SQL Server in VS Code. Nexo SQL Studio combines a database client with dedicated Oracle SQL and PL/SQL tooling.
Before connecting
Use the host, port, database name and credentials supplied by your administrator. Enable the required TLS settings; do not disable certificate validation to work around a connection error.
Enter the PostgreSQL database name and role. Check schema permissions and TLS requirements. For Supabase, use the direct or pooler details provided by the project; IPv4/IPv6 reachability and pooler behavior can affect your workflow.
Connect and run SQL
- Install Nexo SQL Studio and open Connections Explorer.
- Add a connection, select the database engine and enter a unique name.
- Enter the engine-specific fields. Test the connection, resolve any inline errors, then save.
- Open a SQL worksheet from the saved connection and run the example below.
- Inspect the results. Use a disposable database for write examples and review commit/rollback behavior before changing production data.
SELECT current_database(), current_user;Feature availability
Database support does not imply identical features. Connections and SQL worksheets are the starting point; editing, DDL, modeling, transfers, administration and AI operations depend on the engine and workflow. Check the installed version and the relevant guide before relying on an advanced operation.
Free covers core SQL workflows. Pro adds advanced development, delivery and AI/MCP tools. A Pro license does not make an unsupported engine feature available.
Troubleshooting
Check the selected engine, host or file path, database name, account permissions and TLS requirements. Keep the connection editor open while correcting failed tests. Include the engine, server version, extension version and a sanitized error when requesting support; never include passwords or wallet secrets.