Cloud SQL PostgreSQL instances should have 'log_temp_files' set to '0'

Checks that Cloud SQL PostgreSQL instances have the `log_temp_files` database flag set to `0`. Temporary files are not logged by default, and setting `log_temp_files` to `0` makes the instance log all temporary files.

Temporary files are not logged by default. To log all temporary files, a value of 0 should set in the log_temp_files flag.

What this control checks

Cloud SQL PostgreSQL log_temp_files database flag must be set to 0.

Common pitfalls

Temporary files are not logged by default

Temporary files are not logged by default.

Value of -1 disables temporary file logging

A value of -1 disables temporary file information logging. Positive values log only files whose size is greater than or equal to the specified number of kilobytes.

Audit evidence

Evidence that deployed resources meet this control: PowerPipe control gcp_compliance.control.sql_instance_postgresql_log_temp_files_database_flag_0.

Scans of the Terraform code that flag the same setting before deployment: Trivy check GCP-0014.

Framework-specific interpretation

CIS GCP Benchmark v1.2.0: Mapped to 6.2.15 (Ensure that the 'log_temp_files' database flag for Cloud SQL PostgreSQL instance is set to '0').

Framework mappings

The clauses this control is mapped to in each framework.

CIS GCP Benchmark v1.2.0

6.2.15 Ensure that the 'log_temp_files' database flag for Cloud SQL PostgreSQL instance is set to '0'

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

Compliance.tf Control: sql_instance_postgresql_log_temp_files_database_flag_0
Powerpipe Control: gcp_compliance.control.sql_instance_postgresql_log_temp_files_database_flag_0
Trivy Check: GCP-0014

Last reviewed: 2026-10-10

View all Google Cloud controls →