Greengage DB

Based on Greenplum Database Software
Backward compatibility
Full compatibility with the latest minor versions of Greenplum 6 and 7
Open Source
Open Source solution licensed under ASF 2.0
Transparency
Contribute and evolve project with full access to the source code
Scalability
Ideal for fast growing data volumes providing horizontal scalability
Community support
Our community is always ready to help you with your questions about the database
Easy integration
Process existing data from warehouses in Greengage using bunch of connectors, protocols, and data formats

Target features

Planned product features under development
Expand & Shrink
Scale cluster horizontally by dynamic expand and shrink functionality
Legacy GP refactoring
Move Greengage specific code base into PostgreSQL extensions to simplify the process of upgrading PostgreSQL major version
Kernel upgrade to PostgreSQL 16
Greengage allows fast and transparent upgrade to PostgreSQL 16
Enhanced pgAudit
Extend security protection with flexible audit functionality
Advanced password check
Protect data with advanced password policy
Auto failover
Automated switchover from Master to Standby in case of failure

Roadmap

See our development plan for the near future
{Initial Greengage 6.X, 7.X releases with renaming}
{Migration from GP to GREENGAGE}
  • Make CI/CD
  • Migrate ADB to Greengage
  • Public binaries
  • Repository documentation updates
{Preparation for PG upgrade}
  • Separate PXF Cluster
  • Shrink (ggshrink)
  • Decide PG major version for upgrade
  • Refactor GP legacy
{GREENGAGE Release before core upgrade}
  • Implementation pgAudit
  • Advanced password check
  • Raw monitoring metrics GP legacy
  • Auto failover
{Upgrade PostgreSQL version in GREENGAGE}
  • PG core upgrade
  • PG1X related features
{FUTURE ROADMAP}
  • Intersegment query parallelism
  • Code generation / JIT (Just In Time) materialisation
  • Answer Query Using Materialized View

Blog

Technical publications from our team, as well as latest news on Greengage
Separating Orca into a Postgres extension: purpose and implementation details
Separating Orca into a Postgres extension: purpose and implementation details
In this article, we will talk about why we decided to move the Orca query planner from the core of Greengage Database (based on Greenplum) to an extension and how we implemented it
Postgres
ORCA
Greenplum vs Citus. Part 2
Greenplum vs Citus. Part 2
This article is a continuation of the comparison of Greenplum with Citus. Here, we discuss data distribution and cluster balancing
GREENPLUM
Citus
Greenplum vs Citus
Greenplum vs Citus
With this article, we open a series of materials dedicated to a comparative review of distributed DBMS technologies. Let’s start with a comparison of Greenplum with Citus
GREENPLUM
Citus

Grow with the Greengage Community