Google Cloud Compliance ControlsGoogle Cloud SQL
Cloud SQL PostgreSQL instances should have 'log_planner_stats' set to 'off'
The PostgreSQL planner/optimizer is responsible to create an optimal execution plan for each query. The log_planner_stats flag controls the inclusion of PostgreSQL planner performance statistics in the PostgreSQL logs for each query.
What this control checks
Cloud SQL PostgreSQL instances must have the 'log_planner_stats' database flag set to 'off'.
Framework mappings
The clauses this control is mapped to in each framework.
- 6.2.10 Ensure 'log_planner_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'
Related controls
- Cloud SQL PostgreSQL instances should have 'log_hostname' configured appropriately
- Cloud SQL MySQL instances should have 'skip_show_database' set to 'on'
- AlloyDB instances should have 'log_min_messages' set to warning or higher
- Cloud SQL instances should prohibit world-readable access
- Cloud SQL instances should have labels configured
Tool mappings
Use these identifiers to cross-reference this control across tools, reports, and evidence.
- Compliance.tf Control:
sql_instance_postgresql_log_planner_stats_database_flag_off - Powerpipe Control:
gcp_compliance.control.sql_instance_postgresql_log_planner_stats_database_flag_off
Last reviewed: 2026-10-10