PostgreSQL

PostgreSQL is a network SQL engine. Point TableR at an existing server by filling the connection form, or let TableR start a local PostgreSQL for you with the built-in bootstrap when you do not have a server yet.

Overview

TableR speaks the native PostgreSQL wire protocol, so it works with a local install, a container, a managed service (RDS, Cloud SQL, Azure Database, Supabase, Neon, and similar), or a bootstrapped local server. Because these are all PostgreSQL, the same connection fields below apply everywhere; only the values change.

• Local development — connect to 127.0.0.1:5432, or bootstrap a local server.
• Remote / managed — use the provider endpoint and enable SSL/TLS.
• PostgreSQL-compatible engines — CockroachDB, Greenplum, and Amazon Redshift use the same protocol and similar fields.

Before you start

• A reachable PostgreSQL server (host and port), or use Local bootstrap instead.
• A database user (role) name — this is required.
• The user's password, if the server requires one.
• Optionally, the specific database to open on connect.
• For remote servers: network access to the port and, usually, SSL/TLS enabled.

Connection fields

These defaults match TableR's PostgreSQL connection form. Secrets are written to the operating system keyring, never to plain configuration files.

Connect with the form

1. 1
   Choose PostgreSQL

   Open the launcher and pick the PostgreSQL card.

2. 2
   Enter host and port

   Use 127.0.0.1 and 5432 for a local server, or your provider's endpoint for a remote one.

3. 3
   Add credentials

   Type the username, and the password if required. The password is saved to the OS keyring.

4. 4
   Pick a database (optional)

   Set a database to open it directly, or leave it blank to use the role's default.

5. 5
   Enable SSL/TLS for remote

   Turn on SSL/TLS when connecting to a remote or managed server.

6. 6
   Save and connect

   Save the profile so it reappears in the launcher, then connect.

Use a connection string

Instead of filling every field, you can paste a PostgreSQL connection URI. Both postgres:// and postgresql:// schemes are accepted.

postgresql://username:password@host:5432/database?sslmode=require

• Omit the password from the URI and let TableR store it in the keyring instead.
• Append sslmode=require (or verify-full) for remote servers.
• URL-encode special characters in the password (for example @ becomes %40).

Local bootstrap

If you do not have a server, TableR can start a local PostgreSQL for you — no separate install required.

1. 1
   Select PostgreSQL

   Pick PostgreSQL in the launcher.

2. 2
   Choose Local bootstrap

   TableR provisions and starts a local server on your machine.

3. 3
   Start querying

   A connection is created for you; open a SQL tab and run a query.

SSL/TLS

Local servers on 127.0.0.1 usually need no encryption. For anything over a network, enable SSL/TLS. If you connect with a URI, control the behaviour with the sslmode parameter.

• disable — no encryption (local only).
• require — encrypt, but do not verify the server certificate.
• verify-ca / verify-full — encrypt and verify the certificate (most secure).

Verify the connection

Once connected, open a SQL tab and run a quick check:

SELECT version();
SELECT current_database(), current_user;

If both statements return rows, the connection and credentials are working.

Troubleshooting

Next steps