CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - PostgreSQL Database/63 of 83
6.2.10Ensure 'log_planner_stats' database flag for Cloud SQL PostgreSQL instance is set to 'off'
Control family: Cloud SQL Database Services - PostgreSQL Database
Control description
The same SQL query can be excuted in multiple ways and still produce different results. 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.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Planner statistics record how long PostgreSQL spent choosing an execution plan for each query. Like parser statistics (6.2.9), they belong in a short tuning session, not in everyday logging, where they only add volume and cost.
Before you start
The same on every cloud, before the steps in the tabs.
- Record in the PostgreSQL configuration standard that log_planner_stats is off, so every new instance starts with it.
- Agree that it is turned on only for short tuning sessions, and turned off again afterwards.
Evidence
- The PostgreSQL configuration standard
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set the flag on each PostgreSQL instance in Cloud SQL, then watch for instances without it with Security Command Center.
Task 1Set log_planner_stats to off on each PostgreSQL instance
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the PostgreSQL instance and select Edit.
- Expand Database flags (shown as Flags on some instances) and choose Add a database flag, or find the flag if it is already listed.
- Choose log_planner_stats and set it to off, then choose Done.
- Choose Save; if the console says the change restarts the instance, schedule it for a quiet period first.
- Check it: the instance Overview lists log_planner_stats with the value off under Database flags.
Task 2Keep it checked with the Security Health Analytics finding SQL_LOG_PLANNER_STATS_ENABLED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category SQL_LOG_PLANNER_STATS_ENABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set the flag on the instance it names.
- Check it: after the next Security Health Analytics scan, no active SQL_LOG_PLANNER_STATS_ENABLED finding remains.
Evidence
- The Overview of each PostgreSQL instance, listing log_planner_stats set to off under Database flags
- Security Command Center, with no active SQL_LOG_PLANNER_STATS_ENABLED finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.