Vertica Analytics Platform Version 10.0.x Documentation

CONFIGURATION_PARAMETERS

Provides information about configuration parameters currently in use by the system that are configurable at the database, node, or session level.

Column Name Data Type Description
NODE_NAME

VARCHAR

The node names on the cluster for which information is listed.

ALL indicates that all the nodes have the same value.

PARAMETER_NAME

VARCHAR

The name of the configurable parameter. For names of supported parameters, see Configuration Parameter Categories in the Administrator's Guide.

CURRENT_VALUE

VARCHAR

The value of the current setting for the parameter.

RESTART_VALUE

VARCHAR

The value of the parameter 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 default value for the parameter.

CURRENT_LEVEL

VARCHAR

Level at which CURRENT_VALUE is set.

Valid values: Node, database, session, or default.

RESTART_LEVEL

VARCHAR

Level at which the parameter will be set after the next restart.

Valid values: Node, database, or default.

IS_MISMATCH

BOOLEAN

A t (true) setting indicates CURRENT_VALUE and RESTART_VALUE do not match.

GROUPS

VARCHAR

Any group to which the parameter belongs (for example, Security Parameters).

ALLOWED_LEVELS

VARCHAR

Indicates level or levels at which the specified parameter can be set.

Valid values: Node, database, or session.

SUPERUSER_ONLY

BOOLEAN

Indicates if the parameter settings are viewable by the superuser only. If true, the following columns will be masked if viewed by a non-superuser:

  • current_value
  • restart_value
  • database_value
  • default_value
CHANGE_UNDER_SUPPORT_GUIDANCE 

BOOLEAN

A t (true) setting indicates parameters intended for use only by Vertica.

CHANGE_REQUIRES_RESTART

BOOLEAN

Indicates whether the configuration change requires a restart, where t is true and f is false.

DESCRIPTION

VARCHAR

A description of the parameter's purpose.

Example

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 = 'EnableSSL';
-[ RECORD 1 ]-----------------+--------------------------
node_name                     | ALL
parameter_name                | EnableSSL
current_value                 | 0
restart_value                 | 1
database_value                | 0
default_value                 | 0
current_level                 | DEFAULT
restart_level                 | NODE
is_mismatch                   | t
groups                        |
allowed_levels                | NODE, DATABASE
superuser_only                | f
change_under_support_guidance | f
change_requires_restart       | t
description                   | Enable SSL for the server

The following example shows a case where a non-superuser is viewing a parameter where superuser_only is true.

=> \c VMart nonSuperuser
You are now connected to database "VMart" as user "nonSuperuser".
=> SELECT * FROM CONFIGURATION_PARAMETERS WHERE where superuser_only = 't';
-[ RECORD 1 ]-----------------+--------------------------------------
node_name                     | ALL
parameter_name                | LDAPLinkDryRun
current_value                 | ********
restart_value                 | ********
database_value                | ********
default_value                 | ********
current_level                 | DEFAULT
restart_level                 | DEFAULT
is_mismatch                   | f
groups                        |
allowed_levels                | DATABASE
superuser_only                | t
change_under_support_guidance | t
change_requires_restart       | f
description                   | Just contact LDAP server and log the response. Don't perform any changes

See Also

Configuration Parameters in the Administrator's Guide