controls::correct sql statements generating errors are recorded

Overview

The log_min_error_statement setting causes all SQL statements generating errors at or above the specified severity level to be recorded in the server log. Each level includes all the levels that follow it. The lower the level (vertically, below), the fewer messages are recorded. Valid values are:

  • DEBUG5 <– exceedingly chatty
  • DEBUG4
  • DEBUG3
  • DEBUG2
  • DEBUG1
  • INFO
  • NOTICE
  • WARNING
  • ERROR
  • LOG
  • FATAL
  • PANIC <– practically mute ERROR is considered the best practice setting.

Changes should only be made in accordance with your organization’s logging policy.

Note: To effectively turn off logging of failing statements, set this parameter to PANIC.

Excelent Compliance Solution.

Puppet is an excellent solution to ensure your databases are CIS or STIG compliant. Now you’re looking at information about only one compliance control, but managing total compliance isn’t hard either!

If you you like he prospect of easy way into continuous compliancy with minimal fuss and bother, we suggest taking a look at our solution as your go-to option. Plus, our team can help you get up and running so that you can focus on other areas of your business. What are you waiting for? Get started today!

Benchmarks

This control is used in the following benchmarks:

Skipping

To deliberately skip this control (e.g. meaning don’t use Puppet to enforce this setting), we provide you with three ways:

1) Add pg_secured::controls::correct_sql_statements_generating_errors_are_recorded: skip to your hiera data. This will skip this control for ALL databases.
2) Add pg_secured::controls::correct_sql_statements_generating_errors_are_recorded::dbname: skip to your hiera data. This will skip this control for specified database only.
3) Add an entry with the content correct_sql_statements_generating_errors_are_recorded to the array value pg_secured::skip_list in your hiera data.

Attributes

Attribute Name Short Description
title The instance to apply the control to.

title

The instance to apply the control to.

All controls need an instance to apply the control to. Here is a simple example:

pg_secured::controls::control_name { 'instance':}

In this example, the string instance is the instance to apply the control to.

Back to overview of controls::correct_sql_statements_generating_errors_are_recorded