Configuration parameters
Vertica supports a wide variety of configuration parameters that affect many facets of database behavior. These parameters can be set with the appropriate ALTER statements at one or more levels, listed here in descending order of precedence:
-
User (ALTER USER)
-
Session (ALTER SESSION)
-
Node (ALTER NODE)
-
Database (ALTER DATABASE)
Not all parameters can be set at all levels. Consult the documentation of individual parameters for restrictions.
You can query the CONFIGURATION_PARAMETERS system table to obtain the current settings for all user-accessible parameters. For example, the following query returns settings for partitioning parameters: their current and default values, which levels they can be set at, and whether changes require a database restart to take effect:
=> SELECT parameter_name, current_value, default_value, allowed_levels, change_requires_restart
FROM configuration_parameters WHERE parameter_name ILIKE '%partitioncount%';
parameter_name | current_value | default_value | allowed_levels | change_requires_restart
----------------------+---------------+---------------+----------------+-------------------------
MaxPartitionCount | 1024 | 1024 | NODE, DATABASE | f
ActivePartitionCount | 1 | 1 | NODE, DATABASE | f
(2 rows)
In this section
- General parameters
- Azure parameters
- Constraints parameters
- Database Designer parameters
- Eon Mode parameters
- Epoch management parameters
- Google Cloud Storage parameters
- Hadoop parameters
- Internationalization parameters
- Kafka user-defined session parameters
- Kerberos parameters
- Machine learning parameters
- Memory management parameters
- Monitoring parameters
- Numeric precision parameters
- Profiling parameters
- Projection parameters
- S3 parameters
- SNS parameters
- Security parameters
- Stored procedure parameters
- Text search parameters
- Tuple mover parameters