Configuration parameters affect categories of server behaviors, such as resource consumption, query tuning, and authentication. The following topics describe Greenplum configuration parameter categories.
These parameters control how clients connect and authenticate to Greenplum Database.
These parameters set the limits for system resources consumed by Greenplum Database.
These parameters control system memory usage.
Warning: Do not use cost-based vacuum delay because it runs asynchronously among the segment instances. The vacuum cost limit and delay is invoked at the segment level without taking into account the state of the entire Greenplum Database array
You can configure the execution cost of
ANALYZE commands to reduce the I/O impact on concurrent database activity. When the accumulated cost of I/O operations reaches the limit, the process performing the operation sleeps for a while, Then resets the counter and continues execution
These parameters control the usage of GPORCA by Greenplum Database. For information about GPORCA, see About GPORCA in the Greenplum Database Administrator Guide.
These parameters control aspects of SQL query processing such as query operators and operator settings and statistics sampling.
The following parameters control the types of plan operations the Postgres Planner can use. Enable or deactivate plan operations to force the Postgres Planner to choose a different plan. This is useful for testing and comparing query performance using different plan types.
Warning: Do not adjust these query costing parameters. They are tuned to reflect Greenplum Database hardware configurations and typical workloads. All of these parameters are related. Changing one without changing the others can have adverse affects on performance.
These parameters adjust the amount of data sampled by an
ANALYZE operation. Adjusting these parameters affects statistics collection system-wide. You can configure statistics collection on particular tables and columns by using the
ALTER TABLE SET STATISTICS clause.
Control the query plan execution.
These configuration parameters control Greenplum Database logging.
These configuration parameters control Greenplum Database data collection and notifications related to database monitoring.
The following parameters configure the data collection agents that populate the
These parameters enable and configure query metrics collection. When enabled, Greenplum Database saves metrics to shared memory during query execution. These metrics are used by Tanzu Greenplum Command Center, which is included with VMware’s commercial version of Greenplum Database.
These parameters control the server statistics collection feature. When statistics collection is enabled, you can access the statistics data using the pg_stat family of system catalog views.
When automatic statistics collection is enabled, you can run
ANALYZE automatically in the same transaction as an
CREATE TABLE...AS SELECT statement when a certain threshold of rows is affected (
on_change), or when a newly generated table has no statistics (
on_no_stats). To enable this feature, set the following server configuration parameters in your Greenplum Database master
postgresql.conf file and restart Greenplum Database:
Warning: Depending on the specific nature of your database operations, automatic statistics collection can have a negative performance impact. Carefully evaluate whether the default setting of
on_no_stats is appropriate for your system.
These configuration parameters set defaults that are used for client connections.
These configuration parameters set limits for locks and deadlocks.
The following configuration parameters configure the Greenplum Database resource management feature (resource queues), query prioritization, memory utilization and concurrency control.
The following parameters configure the Greenplum Database resource group workload management feature.
The following parameters configure the external tables feature of Greenplum Database.
The following parameter configures default option settings for Greenplum Database tables.
The following parameters configure the append-optimized tables feature of Greenplum Database.
The following parameters provide compatibility with older PostgreSQL and Greenplum Database versions. You do not need to change these parameters in Greenplum Database.
The parameters in this topic control the configuration of the Greenplum Database array and its components: segments, master, distributed transaction manager, master mirror, and interconnect.
Greenplum Database supports only the UDPIFC (default) and TCP interconnect types.
These parameters control the configuration of the replication between Greenplum Database primary master and standby master.
The parameters in this topic control the configuration of the Greenplum Database PL/Java language.
The parameters in this topic control the configuration of the Greenplum Database XML data type.