GPORCA is a cost-based optimizer which is used by Greenplum Database in conjunction with the PostgreSQL planner. It is also known as just ORCA, and Pivotal Optimizer. The code for GPORCA resides src/backend/gporca. It is built automatically by default.
Follow these macOS steps for getting your system ready for GPDB
Follow appropriate linux steps for getting your system ready for GPDB
ORCA requires xerces 3.1 or gp-xerces. For the most up-to-date way of building gp-xerces, see the README at the following repository:
# 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 directory and the TCP ports for the demo cluster can be changed on the fly.
Instead of make cluster, consider:
DATADIRS=/tmp/gpdb-cluster PORT_BASE=5555 make cluster
The TCP port for the regression test can be changed on the fly:
PGPORT=5555 make installcheck-world
To turn GPORCA off and use Postgres planner for query optimization:
set optimizer=off;
If you want to clean all generated files
make distclean
- The default regression tests
make installcheck-world
-
The top-level target installcheck-world will run all regression tests in GPDB against the running cluster. For testing individual parts, the respective targets can be run separately.
-
The PostgreSQL check target does not work. Setting up a Greenplum cluster is more complicated than a single-node PostgreSQL installation, and no-one's done the work to have make check create a cluster. Create a cluster manually or use gpAux/gpdemo/ (example below) and run the toplevel make installcheck-world against that. Patches are welcome!
-
The PostgreSQL installcheck target does not work either, because some tests are known to fail with Greenplum. The installcheck-good schedule in src/test/regress excludes those tests.
-
When adding a new test, please add it to one of the GPDB-specific tests, in greenplum_schedule, rather than the PostgreSQL tests inherited from the upstream. We try to keep the upstream tests identical to the upstream versions, to make merging with newer PostgreSQL releases easier.
Currently, GPDB is built with GPORCA by default. If you want to build GPDB
without GPORCA, configure requires --disable-orca flag to be set.
# Clean environment
make distclean
# Configure build environment to install at /usr/local/gpdb
./configure --disable-orca --with-perl --with-python --with-libxml --prefix=/usr/local/gpdb
gpperfmon tracks a variety of queries, statistics, system properties, and metrics.
To build with it enabled, change your configure to have an additional option
--enable-gpperfmon
See more information about gpperfmon here
gpperfmon is dependent on several libraries like apr, apu, and libsigar
GPDB supports Python3 with plpython3u UDF
See how to enable Python3 for details.
See Building GPDB client tools on Windows for details.
See README.docker.md.
We provide a docker image with all dependencies required to compile and test
GPDB (See Usage). You can view the dependency dockerfile at ./src/tools/docker/centos6-admin/Dockerfile.
The image is hosted on docker hub at pivotaldata/gpdb-dev:centos6-gpadmin.
A quickstart guide to Docker can be found on the Pivotal Engineering Journal.
There is a Vagrant-based quickstart guide for developers.