# Enable log_checkpoints Parameter on Azure PostgreSQL Servers for Improved Monitoring and Troubleshooting

- Source: https://support.icompaas.com/support/solutions/articles/62000234792-enable-log-checkpoints-parameter-on-azure-postgresql-servers-for-improved-monitoring-and-troubleshoot
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [Azure Database Services Benchmark v1.0.0](https://support.icompaas.com/support/solutions/62000112693) › [Azure Database Services Benchmark](https://support.icompaas.com/support/solutions/folders/62000169261)
- Last updated: 2026-05-29
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**Profile Applicability:**

-   **Level 1**  
    

**Description:** Enabling the log\_checkpoints parameter ensures that PostgreSQL logs every checkpoint, which is a crucial part of PostgreSQL's write-ahead log mechanism. These logs help track the progress of the database’s recovery process and can be invaluable for troubleshooting, detecting performance issues, and ensuring data consistency.

**Rationale:** Enabling log\_checkpoints ensures that each checkpoint is logged, providing better visibility into how frequently data is being written to the disk and when checkpoints are happening. This is critical for monitoring system performance, detecting potential issues, and ensuring compliance with auditing and security standards.

**Impact:**

-   Pros:  
    
    -   Provides insight into database recovery operations.  
        
    -   Helps monitor the frequency and performance of checkpoints.  
        
    -   Essential for troubleshooting and performance tuning.  
        
-   Cons:  
    
    -   Additional log entries can increase the storage requirements.  
        
    -   High-traffic systems could produce large amounts of log data.  
        

**Default Value:**

The default value for log\_checkpoints is OFF.

**Pre-requisites:** Ensure that logging is enabled for PostgreSQL and that the logs are being managed properly to avoid excessive storage consumption.

**Remediation**

**Test Plan:**

**Using Azure Portal:**

1.  Log in to the Azure Portal: [https://portal.azure.com](https://portal.azure.com/).  
    
2.  Navigate to Azure Database for PostgreSQL servers.  
    
3.  Select the desired PostgreSQL database.  
    
4.  Under Settings, click on Server parameters.  
    
5.  Search for the log\_checkpoints parameter.
    
6.  Ensure the value is set to ON.  
    

**Using Azure CLI:**1\. Run the following command to verify the log\_checkpoints setting:

az postgres server configuration show --resource-group <resource-group-name> --server-name <server-name> --name log\_checkpoints

  

-   The output should show log\_checkpoints as ON.  
    

**Implementation Plan:**

**Using Azure Portal:**

1.  Go to Azure Database for PostgreSQL servers.  
    
2.  Select the database server.  
    
3.  Under Settings, click on Server parameters.  
    
4.  Set the log\_checkpoints parameter to ON and save.
    

**Using Azure CLI:**1\.  To enable the log\_checkpoints parameter, use the following command:

az postgres server configuration set --resource-group <resource-group-name> --server-name <server-name> --name log\_checkpoints --value ON

  

**Backout Plan:**

**Using Azure Portal:**

1.  Go to Azure Database for PostgreSQL servers.  
    
2.  Under Settings, click on Server parameters.  
    
3.  Set the log\_checkpoints parameter back to OFF if necessary.
    

**Using Azure CLI:** 1. To disable the log\_checkpoints parameter, use the following command:

az postgres server configuration set --resource-group <resource-group-name> --server-name <server-name> --name log\_checkpoints --value OFF

  

**References:**

-   [Configure PostgreSQL Server Parameters  
    ](https://docs.microsoft.com/en-us/azure/postgresql/howto-configure-server-parameters-using-portal)
    
-   [PostgreSQL Server Configuration for Logging](https://learn.microsoft.com/en-us/powershell/module/az.postgresql/update-azpostgresqlconfiguration?view=azps-9.2.0#example-1-update-postgresql-configuration-by-name)

## 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.
