How to Configure Greenplum Audit Log
To set up a greenplum audit log, enable server statement logging across all database nodes. You must also load the native audit module to track object and role events. Data teams often turn on these logs to meet strict security rules. Still, broad database roles make it hard to trace actions back to one person. When five engineers share one admin role, the log only shows the shared role name. Teams then struggle to see who ran a bad query during an incident. How the native greenplum audit log
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.
To set up a greenplum audit log, enable server statement logging across all database nodes. You must also load the native audit module to track object and role events. Data teams often turn on these logs to meet strict security rules. Still, broad database roles make it hard to trace actions back to one person. When five engineers share one admin role, the log only shows the shared role name. Teams then struggle to see who ran a bad query during an incident.
How the native greenplum audit log works
Greenplum runs as a distributed database with one coordinator node and many segment nodes. A user sends a query to the coordinator node first. The coordinator then builds a query plan and sends work to the segment nodes. Because of this split design, each node writes its own local log file. The coordinator log records the main SQL text that the user sent. Segment logs record the smaller tasks that run on the actual data slices.
Standard server logs capture basic login attempts, system errors, and full SQL statements. For deeper tracking, teams turn on the native PostgreSQL audit extension inside the cluster. This extension watches for reads, writes, table changes, and role updates on specific tables. Admins set logging rules at the server level or for specific database roles. Every node writes these audit events into comma-separated files on its local disk. Teams then use cluster tools or log shippers to pull these files together.
Managing log volume across segment nodes
Distributed logging creates massive file volume very fast on busy analytics clusters. A single query on the coordinator can trigger dozens of tasks on segment nodes. If you log every statement on every segment, disks fill up in days. High disk usage from heavy logging also slows down active data warehouse queries. To fix this, most admins only log full statements on the coordinator node. They leave segment logs set to capture only fatal errors and system crashes.
Even on the coordinator node, audit files grow large when BI apps run queries. Automated reporting tools send thousands of select statements every hour under one service account. Admins must set up log rotation rules to clear out old files each day. They also ship these text files to central storage for long-term security reviews. Without strict filters, vital security alerts get lost inside millions of routine read logs.
Audit Log Integrity + End-to-End Encryption: architecture patterns and best practices
Continue reading? Get the full guide.
Free. No spam. Unsubscribe anytime.
What native audit logs solve and what they miss
Native audit logs give you a solid history of database activity after the fact. They prove that a query ran at a specific time under a specific role. Security teams use these records to check past events during a compliance review. Still, native logging only records what happened after the query starts running. It cannot stop a dangerous drop or delete statement while it is in flight.
Native logs also cannot fix the problem of shared database accounts. If an admin logs in with a shared role, the log misses their true identity. Also, native logs record raw query results without hiding sensitive user fields. They do not rewrite emails, phone numbers, card numbers, or national IDs in results. Anyone with read rights on the table gets the full data on their screen. The audit log simply notes that the read happened, leaving data exposure risks open.
Govern statements and responses across databases and APIs
Good config and scoped roles are needed setup. They do not check single queries in flight or mask sensitive fields in returned rows. Across Postgres, MySQL, SQL Server, MongoDB, ClickHouse, Kubernetes APIs, SSH, and internal HTTP endpoints, hoop.dev sits inline in the protocol beside each supported service as an open-source proxy, a sidecar for your database or API. For every query or command an AI agent or engineer runs against production, hoop.dev decides to pass, mask, block, or hold it for human approval.
First, hoop.dev guardrails block banned queries before they run or hold risky ones for review, and hoop.dev data masking rewrites matched sensitive values in responses in memory. Furthermore, hoop.dev holds SOC 2 Type II and is open source on GitHub.
Frequently asked questions
Where does Greenplum store its native audit log files?
Each coordinator and segment node stores its own log files in a local folder. Admins must collect files from all hosts to build a full cluster view.
Does turning on full statement logging slow down Greenplum queries?
Yes, logging every query on all nodes adds heavy disk write work. Most teams log statements only on the coordinator node to protect cluster speed.
Can the native greenplum audit log block a bad query before it runs?
No, the native log only writes down events as they happen on the server. It cannot pause a query for approval or rewrite fields in the output.
Related guides
In this post