We've forked here the original GPDB repository after Greenplum became a closed-source project. And continue to make it production-ready.
The main goal is:
- to fix bugs, especially those leading to core dump master/segment processes;
- to adopt existing GP/PG extensions for the latest stable GP version;
- backporting stable features from other projects (Postgres > 9.4, Cloudberry);
- creating a new stable version (7.X) by fixing everything we stumble upon.
The current last stable version is 6X. It's used by major of our clients and partners.
If you want to try it right away - https://yandex.cloud/en/services/managed-greenplum
You can check our open-gpdb roadmap 2024/2025 to see the product plans and goals we want to achieve in 2024/2025. Welcome to share your thoughts and ideas.
See detailed instruction about building, testing, build options, using Docker and Vagrant in Build readme
# Configure build environment to install at /usr/local/gpdb
./configure --with-perl --with-python --with-libxml --with-gssapi --prefix=/usr/local/gpdb --without-mdblocales
# Compile and install
make -j8
make -j8 install
# Bring in greenplum environment into your running shell
source /usr/local/gpdb/greenplum_path.sh
# Start demo cluster
make create-demo-cluster
# (gpdemo-env.sh contains __PGPORT__ and __MASTER_DATA_DIRECTORY__ values)
source gpAux/gpdemo/gpdemo-env.sh
The default regression tests
make installcheck-world
This is the main repository for Greenplum Database. Alongside this, there are several ecosystem repositories for the Cloudberry Database, including the website, extensions, connectors, adapters, and other utilities.
- open-gpdb/yezzey: Extension to fast offload/download AO/AOCS data to/from S3.
- open-gpdb/yproxy: GP <-> S3 proxy for schedule and limit requests rate from hot to S3
- open-gpdb/pgaudit: PGAudit extension for GP
- open-gpdb/gp_relaccess_stats: Greenplum extension to collect stats on table operations like SELECT/UPDATE/INSERT/DELETE/TRUNCATE
- open-gpdb/gp_relsizes_stats: Greenplum extension to collect statistics on the distribution of memory occupied by tables and files on segment hosts.
- open-gpdb/pxf: Platform Extension Framework (PXF) for Greenplum Database.
- wal-g Database physical backup/restore tool
- cloudberry New MPP Database compatible with Greenplum Database
- odyssey Pooler for GP
- gpdb Archived original Greenplum Database
We have many channels for community members to discuss, ask for help and feedback:
| Type | Description |
|---|---|
| Q&A | Ask for help when running/developing, visit GitHub Discussions - QA. |
| New ideas / Feature Requests | Share ideas for new features, visit GitHub Discussions - Ideas. |
| Report bugs | Problems and issues in database core. If you find bugs, welcome to submit them here. |
| Report a security vulnerability | View our security policy to learn how to report and contact us. |
| Community events | Including meetups, webinars, conferences, and more events, visit the Events page and subscribe events calendar. |
| Documentation | Official documentation for Managed Database. You can explore it to discover more details about us. |
Open-gpdb is a free and open project and we appreciate to receive contributions from our community.
If you would like to contribute a new feature or a bug fix, please discuss your idea first on the GitHub issue. If there is no issue for your idea, please open one. It may be that somebody is already working on it, or that there are some complex obstacles that you should know about before starting the implementation. Usually there are several ways to fix a problem and it is important to find the right approach before spending time on a PR that cannot be merged.
To make a contribution you should submit a pull request. There will probably be discussion about the pull request and, if any changes are needed, we would love to work with you to get your pull request merged.
Follow this link to have more information about build and test system: Build readme
Thanks to PostgreSQL, Greenplum Database and other great open source projects to make our project has a sound foundation.
Our patches are released under the Apache License, Version 2.0. Some components may have PostgreSQL License if it is explicity mentioned in the NOTICE file.
