Greenplum

Greenplum is a massively parallel analytics warehouse built on PostgreSQL, so TableR connects to it exactly like PostgreSQL. Fill the connection form to point at your Greenplum coordinator.

Overview

Because Greenplum is PostgreSQL-compatible, the same connection fields and connection strings as PostgreSQL apply. You connect through the coordinator host, and Greenplum spreads the query across its segments.

• Connect through the coordinator — TableR talks to the coordinator host on port 5432.
• Remote / managed — use the provider endpoint and enable SSL/TLS.
• PostgreSQL-compatible — fields, connection strings, and behaviour match PostgreSQL; see the PostgreSQL guide for anything not covered here.

Before you start

• A reachable Greenplum coordinator (host and port).
• A database user name — this is required.
• The user's password, if the warehouse requires one.
• Optionally, the specific database to open on connect.
• For remote warehouses: network access to the port and, usually, SSL/TLS enabled.

Connection fields

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

Connect with the form

1. 1
   Choose Greenplum

   Open the launcher and pick the Greenplum card.

2. 2
   Enter host and port

   Use 127.0.0.1 and 5432 for a local coordinator, or your coordinator endpoint for a remote warehouse.

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 user's default.

5. 5
   Enable SSL/TLS for remote

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

6. 6
   Save and connect

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

Use a connection string

Because Greenplum is PostgreSQL-compatible, you can paste a PostgreSQL connection URI. Both postgres:// and postgresql:// schemes are accepted.

postgresql://username:password@coordinator: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 warehouses.
• URL-encode special characters in the password (for example @ becomes %40).

SSL/TLS

Local coordinators 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