# Ensure Server Parameter 'log_checkpoints' is set to 'ON' for PostgreSQL Database Server

- Source: https://support.icompaas.com/support/solutions/articles/62000229879-ensure-server-parameter-log-checkpoints-is-set-to-on-for-postgresql-database-server
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [General](https://support.icompaas.com/support/solutions/62000037933) › [Azure Compliance / Control / Check](https://support.icompaas.com/support/solutions/folders/62000168797)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

Description:

This control ensures that the PostgreSQL server parameter log\_checkpoints is enabled (set to ON). When enabled, PostgreSQL logs information about checkpoints, including the start and end times, the number of buffers written, and the duration. Checkpoint logging helps database administrators monitor database performance, detect unusual activity, and troubleshoot issues such as I/O bottlenecks or long checkpoint durations.

  

Rationale:

-   Performance Monitoring: Checkpoints can impact database performance; logging them allows administrators to track checkpoint frequency, duration, and buffer writes.
    
-   Troubleshooting: Helps identify and diagnose performance degradation, I/O spikes, or other database anomalies.
    
-   Operational Awareness: Provides visibility into internal database operations for proactive optimization.
    
-   Compliance & Auditing: Logging critical database activities supports auditing requirements and operational transparency.
    

  

Impact:

-   Improves visibility into database internal operations, aiding in proactive monitoring and performance tuning.
    
-   Supports troubleshooting for long-running checkpoints or database slowdowns.
    
-   Helps meet compliance and audit requirements by capturing operational logs.
    

  

Default Value:

-   By default, in PostgreSQL, log\_checkpoints is set to ON.
    
-   PostgreSQL Server Must Use a Flexible Server or a Single Server with Configurable Parameters.
    

  

Pre-requisites:

-   Global Administrator or Security Administrator permissions.
    
-   Must be Azure Database for PostgreSQL – Flexible Server (or Single Server if the parameter is supported).
    

  

Test Plan:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for and open the Azure Database for PostgreSQL
    
3.  Select the target PostgreSQL server
    
4.  From the left menu, under settings,  select Server parameters
    
5.  Search for the parameter log\_checkpoints
    
6.  Verify log\_checkpoints is set to ON
    
7.  If log\_checkpoints is not set to ON, follow the implementation steps
    

  

![](https://support.icompaas.com/assets/kb/bbdd8fb0bcd69340.png)

  

Implementation Steps:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for your Azure Database for PostgreSQL server (Single or Flexible).
    
3.  On the left-hand menu, under Settings, select server parameters.
    

  

                                                  ![](https://support.icompaas.com/assets/kb/9607af9f9b0977a2.png)

  

4.  Search for log\_checkpoints in the server parameters.
    

          ![](https://support.icompaas.com/assets/kb/b344685754a2a919.png)

5.  Set its value to ON (If you keep the log\_checkpoints OFF). Save the changes
    

  

BackOut Plan:

1.  Sign in to the Azure Portal at [https://portal.azure.com](https://portal.azure.com/)
    
2.  Search for and open the Azure Database for PostgreSQL server
    
3.  From the left-hand menu, under settings, select Server parameters
    
4.  Locate the parameter log\_checkpoints
    
5.  Set log\_checkpoints to OFF
    
6.  Save the changes
    

  

Reference:

-   [https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-server-parameters](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-server-parameters)

## Related compliance guidance

- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Configuration checks like this one are the technical half of a SOC 2 / ISO 27001 programme — the guide shows where they fit, what else an auditor expects, and how to evidence them.
- [ISO/IEC 27001:2022 compliance: a practical implementation guide](https://support.icompaas.com/compliance/iso-27001-2022): ISO 27001 Annex A.8 (technological controls) is where cloud hardening evidence lands; the guide shows how to run the ISMS around it.