X100 offers the option to automatically rotate the log file if its size surpasses a specified limit (for example, 1GB or 2GB) or if a specified time interval has passed (e.g. every 30 days). It also includes the option of automatically compressing the rotated log file to .gz format. For more information, see X100 Configuration Parameters.

When you specify a fixed time interval for Automatic Log Rotation, the log rotation will not always happen precisely after the specified time, but only the next time data is written to the log file.

The log file size check is performed at an interval of 15 minutes to check and compare the log file's size to the size limit specified in the configuration, but only when data is written to the log file.

In order to make one of the options persistent (i.e. remains valid even if the database is shut down), it has to be specified under the [server] section in vectorwise.conf.

If a non-valid value is provided to one of the options, then the last valid value will remain active (e.g., setting vwlog_rotation_use_size_threshold='xyz' will not have any effect on the option). Non-valid means either bogus data or values that are not between the lower and the upper bound for the size, respectively time-thresholds. This is applicable for invalid changes during runtime.

To modify the new options during runtime, you must use the CALL X100 syntax.

When the GLOBAL parameter is used, the setting remains in effect until the server is shutdown and for the duration of the session when omitted.

Error logging configuration can be changed dynamically, for example, if you want to increase the logging level while debugging a process. The VWLOG_RELOAD system call loads a specific X100 error log configuration file, whose rules are used for all subsequent log events. Restarting Vector is not necessary.

For example, the following statement enables Vector to immediately start using the specified log configuration file on Windows:

For more information, see VWLOG_RELOAD in the SQL Language Guide.