CONFIGURATION_PARAMETERS
Provides information about all configuration parameters that are currently in use by the system.
Column Name | Data Type | Description |
---|---|---|
NODE_NAME | VARCHAR |
Node names of the database cluster. ALL indicates that all nodes have the same value. |
PARAMETER_NAME | VARCHAR | The parameter name. |
CURRENT_VALUE | VARCHAR | The parameter's current setting. |
RESTART_VALUE | VARCHAR | The parameter's value after the next restart. |
DATABASE_VALUE | VARCHAR | The value that is set at the database level. If no database-level value is set, the value reflects the default value. |
DEFAULT_VALUE | VARCHAR | The parameter's default value. |
CURRENT_LEVEL | VARCHAR |
Level at which CURRENT_VALUE is set, one of the following:
|
RESTART_LEVEL | VARCHAR |
Level at which the parameter will be set after the next restart, one of the following:
|
IS_MISMATCH | BOOLEAN | Whether CURRENT_VALUE and RESTART_VALUE match. |
GROUPS | VARCHAR |
A group to which the parameter belongs—for example, OptVOptions. NoteMost configuration parameters do not belong to any group. |
ALLOWED_LEVELS | VARCHAR |
Levels at which the specified parameter can be set, a comma-delimited list of any of the following values:
|
SUPERUSER_VISIBLE_ONLY | BOOLEAN |
Whether non-superusers can view all parameter settings. If true, the following columns are masked to non-superusers:
|
CHANGE_UNDER_SUPPORT_GUIDANCE | BOOLEAN | Whether the parameter is intended for use only under guidance from Vertica technical support. |
CHANGE_REQUIRES_RESTART | BOOLEAN | Whether the configuration change requires a restart. |
DESCRIPTION | VARCHAR | Describes the parameter's usage. |
Examples
The following example shows a case where the parameter requires a restart for the new setting to take effect:
=> SELECT * FROM CONFIGURATION_PARAMETERS WHERE parameter_name = 'RequireFIPS';
-[ RECORD 1 ]-----------------+----------------------
node_name | ALL
parameter_name | RequireFIPS
current_value | 0
restart_value | 0
database_value | 0
default_value | 0
current_level | DEFAULT
restart_level | DEFAULT
is_mismatch | f
groups |
allowed_levels | DATABASE
superuser_visible_only | f
change_under_support_guidance | f
change_requires_restart | t
description | Execute in FIPS mode
The following example shows a case where a non-superuser is viewing a parameter with restricted visibility:
=> \c VMart nonSuperuser
You are now connected to database "VMart" as user "nonSuperuser".
=> SELECT * FROM CONFIGURATION_PARAMETERS WHERE superuser_visible_only = 't';
-[ RECORD 1 ]-----------------+-------------------------------------------------------
node_name | ALL
parameter_name | S3BucketCredentials
current_value | ********
restart_value | ********
database_value | ********
default_value | ********
current_level | DEFAULT
restart_level | DEFAULT
is_mismatch | f
groups |
allowed_levels | SESSION, DATABASE
superuser_visible_only | t
change_under_support_guidance | f
change_requires_restart | f
description | JSON list mapping S3 buckets to specific credentials.