Secondary PostgreSQL database grows extremely large

Product

Security Management

Version

R81.10 (EOS), R81.20, R82

OS

Gaia

Last Modified

2025-08-04

Symptoms

• PostgreSQL Database on the Secondary High Availability Management Server is larger than the Primary Management Server.
  • To compare the size of the database, run this command on the Primary and Secondary Management servers:

du -h /opt/CPshrd-R81.10/database/postgresql/

• To view the count size, run this command on the Primary and Secondary Management servers:

psql_client cpm postgres -c "select count(*) from pg_largeobject;"

Cause

In the Secondary HA Management server, the pg_largeobject table in the PostgreSQL database keeps growing. It does not delete the floating objects in the table during synchronization.

Solution

This problem was fixed. The fix is included in:

• Jumbo Hotfix Accumulator for R82 starting from Take 36
• Jumbo Hotfix Accumulator for R81.20 starting from Take 111
• Jumbo Hotfix Accumulator for R81.10 starting from Take 177

If you choose not to upgrade, Check Point can supply a Hotfix. Contact Check Point Support to get a Hotfix for this issue.

A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.

For faster resolution and verification, please collect CPinfo files from the Security Management Server and Security Gateways involved in the case.

Hotfix installation instructions:

Refer to sk168597 - How to install a Hotfix.

NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

Article Properties

Access Level: General
Status: Approved by TAC
Date Created: 2024-12-09
Last Modified: 2025-08-04