Administering the gpperfmon Database
Data collected by gpmmon and gpsmon agents is stored in a dedicated database called gpperfmon. This database requires the typical database maintenance tasks, such as clean up of old historical data and periodic
See the gpperfmon Database Reference section for a reference of the tables and views in the gpperfmon database.
Database administrators can connect directly to the gpperfmon database using any Greenplum Database-compatible client program (such as
psql). For example:
$ psql -d gpperfmon -h master_host -p 5432 -U gpadmin
The history tables of the gpperfmon database can be backed up and restored using the Greenplum Database backup and restore utilities. See the Greenplum Database Utility Guide for more information.
Because the gpperfmon database has a small number of tables, you may prefer to devise a backup plan using the table-level backup features of
gp_dump. For example, you can create scripts to run
gp_dump to back up the monthly partitions of the historical data tables on a monthly schedule. Alternately, you can back up your gpperfmon database at the database level.
All of the
*_history tables stored in the gpperfmon database are partitioned into monthly partitions. A January 2010 partition is created at installation time as a template partition. It can be deleted once some current partitions are created. The Command Center agents automatically create new partitions in two month increments as needed. Administrators must periodically drop partitions for the months that are no longer needed in order to maintain the size of the database.
See the Greenplum Database Administrator Guide for more information on dropping partitions of a partitioned table.