Projection Parameters

The following configuration parameters help you manage projections.

Query system table CONFIGURATION_PARAMETERS to determine what levels (node, session, database) are valid for a given parameter.

Parameters Description


Specifies how often Vertica checks the number of projection rows and whether the threshold set by ARCCommitPercentage has been crossed.

For more information, see Collecting Database Statistics.

Default: 86400 seconds (24 hours)


Sets the threshold percentage of WOS to ROS rows, which determines when to aggregate projection row counts and commit the result to the catalog. Vertica performs this action when the WOS to ROS percentage exceeds this setting.

Default: 3 (percent)


Specifies how many ROS containers Vertica creates per projection before ROS pushback occurs.

Increasing this parameter's value can cause serious degradation of database performance. Vertica strongly recommends that you not modify this parameter without first consulting with Customer Support professionals.

Default: 1024


Specifies whether you can create live aggregate projections. For more information, see Live Aggregate Projections.

Default: 1 (enable)


Specifies whether you can create projections that use expressions to calculate column values. For more information, see Aggregating Data Through Expressions.

Default: 1 (enable)


When set to 1, you can create Top-K projections that let you retrieve Top-K data quickly. For more information, see Top-K Projections.

Default: 1 (enable)


Specifies the number of columns (0 –1024) to use in an auto-projection's hash segmentation clause. Set to 0 to use all columns.

Default: 8


Specifies the number of columns (0 –1024) to use in an auto-projection's sort expression. Set to 0 to use all columns.

Default: 8


By default, prior to performing a rebalance, Vertica performs a system table query to compute the size of all projections involved in the rebalance task. This query enables Vertica to optimize the rebalance to most efficiently utilize available disk space. This query can, however, significantly increase the time required to perform the rebalance.

By disabling the system table query, you can reduce the time required to perform the rebalance. If your nodes are low on disk space, disabling the query increases the chance that a node runs out of disk space. In that situation, the rebalance fails.

Default: 1 (enable)


Determines whether auto-projections are segmented if the table definition omits a segmentation clause. You can set this parameter at database and session scopes.

Default: 1 (create segmented auto projections)