Open search page
Hello, I’m DocuDroid!
Open Ask AI page
Submitting feedback
Thank you for rating our AI Search!
We would be grateful if you could share your thoughts so we can improve our AI Search for you and other readers.
GitHub

gppkg

Installs Greengage DB extensions in .gppkg format, such as PL/Java, PL/R, PostGIS, and MADlib, along with their dependencies, across an entire cluster.

Synopsis

gppkg [-i <package> | -u <package> | -r <name>-<version> | -c]
      [-d <master_data_directory>]
      [-a]
      [-v]

gppkg --migrate <GPHOME_old> <GPHOME_new>
      [-a]
      [-v]

gppkg [-q | --query] <query_option>

gppkg -? | -h | --help

gppkg --version

Description

The Greengage DB package manager utility gppkg installs Greengage DB extensions, along with any dependencies, on all hosts across a cluster. It will also automatically install extensions on new hosts in the case of system expansion and segment recovery.

Examples of database extensions and packages that are delivered using the Greengage DB Package Manager are:

  • PL/Java

  • PL/R

  • PostGIS

  • MADlib

Options

-a

Do not prompt the user for confirmation.

-c | --clean

Reconcile the package state of the cluster to match the state of the master host. Running this option after a failed or partial install/uninstall ensures that the package installation state is consistent across the cluster.

-d <master_data_directory>

The master data directory. If not specified, the value set for MASTER_DATA_DIRECTORY will be used.

-i <package> | --install=<package>

Install the given package. This includes any pre- and post-installation steps and installation of any dependencies.

--migrate <GPHOME_old> <GPHOME_new>

Move packages from another GPHOME directory when migrating from one Greengage DB version to another.

For example:

$ gppkg --migrate /usr/local/gpdb-<old-version> /usr/local/gpdb-<new-version>
NOTE

In general, it is best to avoid using the --migrate option, and packages should be reinstalled, not migrated.

When migrating packages, these requirements must be met:

  • At least the master instance of the destination Greengage DB must be started (the instance installed in GPHOME_new). Before running the gppkg command, start the Greengage DB master with the command gpstart -m.

  • Run the gppkg utility from the GPHOME_new installation.

-q | --query <query_option>

Provide information specified by query_option about the installed packages. Only one query_option can be specified at a time. The following table lists the possible values for query_option. package_file is the name of a package.

query_option Returns

<package_file>

Whether the specified package is installed

--info <package_file>

The name, version, and other information about the specified package

--list <package_file>

The file contents of the specified package

--all

List of all installed packages
-r <name>-<version> | --remove=<name>-<version>

Remove the specified package.

-u <package> | --update=<package>

Update the given package.

CAUTION

The process of updating a package includes removing all previous versions of the system objects related to the package. For example, previous versions of shared libraries are removed. After the update process, a database function will fail when it is called if the function references a package file that has been removed.

--version

Display the version of this utility.

-v | --verbose

Set the logging level to verbose.

-? | -h | --help

Display help.

Previous
gpmovemirrors
Next
gprecoverseg