Detections
Analytics
3.1.15 Ensure the correct SQL statements generating errors are recorded
Warning! Audit Deprecated
This audit has been deprecated and will be removed in a future update.
View Next Audit VersionInformation
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 <-- default
- 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
If this is not set to the correct value, too many erring or too few erring SQL statements may be written to the server log.
Solution
Execute the following SQL statement(s) as superuser to remediate this setting (in the example, to error ):postgres=# alter system set log_min_error_statement = 'error';
ALTER SYSTEM
postgres=# select pg_reload_conf();
pg_reload_conf
----------------
t
(1 row)
See Also
Item Details
Audit Name: CIS PostgreSQL 17 v1.0.0 L1 PostgreSQL
References: CSCv7|6.4
Plugin: PostgreSQLDB
Control ID: f28b422a6605a06523cb2a8bf095723ac7741525847bcb46d0985cae9943d616