How to Configure Greenplum Proxy

Published
Length
3 min read

Luis Felipe Dias

All posts

You set up a greenplum proxy by placing a routing node before your coordinator host. This middle step directs client traffic and manages open database sessions. Data teams often use standard connection poolers for this job. Still, shared database roles often grant users too much power across all schemas. One wide role lets an analyst read or change sensitive tables by mistake. How a native greenplum proxy setup works Greenplum runs on a coordinator node and many segment hosts. Users never tal

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

You set up a greenplum proxy by placing a routing node before your coordinator host. This middle step directs client traffic and manages open database sessions. Data teams often use standard connection poolers for this job. Still, shared database roles often grant users too much power across all schemas. One wide role lets an analyst read or change sensitive tables by mistake.

How a native greenplum proxy setup works

Greenplum runs on a coordinator node and many segment hosts. Users never talk to the segment hosts on their own. Every SQL query goes through the coordinator host first. The coordinator checks host rules and user roles before running any query. When many apps and analysts log in, the coordinator runs out of memory.

To fix this load issue, teams add a connection pooler in front. This pooler acts as a basic traffic router for the cluster. It holds a fixed number of open links to the coordinator node. When a user logs in, the pooler assigns an open link from its pool. When the user finishes a query, the link goes back to the pool.

Admins also set up host access files on the coordinator node. These files list which IP addresses can talk to the database. They also state which login method each user group must use. Some teams link the coordinator to an outside directory service for password checks. Once the user passes the login check, the session starts.

What native routing solves and what it misses

This standard setup solves connection limits and stops basic network scans. The coordinator node keeps steady memory use during peak traffic hours. Admins can manage user groups in one central directory service. Host files block unknown networks from reaching the login prompt.

Yet this native setup only checks who can log in at the start. Once a session begins, the pooler passes every query straight to the coordinator. The database relies only on static role grants to control table access. If an engineer needs to check one production bug, they get a broad role. That role stays active long after they fix the bug.

Database Proxy (ProxySQL, PgBouncer) + End-to-End Encryption: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

Static roles also fail to filter private data inside a table. If a user can read a customer table, they get every column in full by default. Queries return raw emails, phone numbers, card numbers, and national IDs in plain text. Data masking would rewrite matched fields in results, but standard poolers lack this feature. Native logs also store queries on local disks, making central audits hard to run.

Managing shared roles across analytics teams

Analytics teams often share service accounts to run scheduled reports and dashboards. Sharing one login makes it hard to track who ran a bad query. When a slow query locks a table, the log only shows the shared role. Admins cannot tie that specific query back to a single person on the team.

Rotating passwords for these shared roles also causes downtime for reporting tools. Every time an admin changes a password, ten different apps might break at once. Because of this pain, teams leave old passwords in place for years. A better setup ties every single query to an individual user identity.

Check database and API queries on the wire

Identity tools, roles, and network rules decide who opens a session. Setup alone cannot check what each query does or mask sensitive values in a response once a session starts. When workflows touch Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, or internal HTTP APIs, hoop.dev sits inline in the wire protocol beside those services as an open-source proxy, a sidecar for your Postgres or API. On every query an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human review.

Your login details and client tools stay as they are while hoop.dev guardrails refuse bad deletes or drops before they run, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II, is MIT licensed, and writes every query and decision to an audit trail that generates evidence for HIPAA, GDPR, and PCI DSS. See the source on GitHub.

Frequently asked questions

Does a connection pooler mask private data in Greenplum query results?

No, standard connection poolers only manage network links and session slots. They do not inspect SQL results or rewrite emails, phone numbers, or card numbers.

Where do clients connect in a Greenplum cluster?

Clients always connect to the main coordinator host or a pooler in front. The coordinator then plans the query and sends work to the segment hosts.

Why are static database roles risky for production support?

Static roles give engineers standing rights to read or alter data at any time. If someone steals a laptop or password, the attacker gets those same permanent rights.

The query runs. The emails stay hidden.