Software Alert — MIRIA202601 — PostgreSQL Internal Database Consistency

Advisory ID: MIRIA202601
Product: Miria 4.4 & 4.5
Category: Software Alert
Last updated: 11 July 2026 — Product Team

A defect has been identified in the PostgreSQL database engine embedded in Miria 4.4 and 4.5.

Under specific operating conditions, this defect may cause premature truncation of transaction status data, which can lead to an inconsistency in the Miria internal (catalog) database, potentially making data inaccessible.

This is not a security vulnerability. It is a data consistency issue related to the embedded database engine.

Affected versions

• Miria 4.4.x prior to 4.4.0.19 — only if running PostgreSQL 17
• Miria 4.5.x prior to 4.5.1.1 — only if running PostgreSQL 17

Installations upgraded from Miria 4.2 or 4.3 still running PostgreSQL 13 or 14 are not affected.

Root cause

The issue originates from the PostgreSQL engine’s handling of certain in-place catalog updates. In rare conditions, these updates were not correctly logged before becoming visible to other sessions, which could allow internal transaction tracking data to become inconsistent and be reclaimed too early. This was fixed upstream by the PostgreSQL Global Development Group in PostgreSQL 17.8 (“Fix issues around in-place catalog updates”).

Resolution

Atempo has released a patch embedding PostgreSQL 17.10, which includes the fix described above.

• Miria 4.5 (→ 4.5.1.1): available 11 July 2026
• Miria 4.4 (→ 4.4.0.19): available 11 July 2026

Recommended actions

1. Apply the patch as soon as possible on all Miria 4.4 / 4.5 instances
2. Log in to your Atempo support portal, download the patch for your Miria version and all deployed OS, and apply it on your Miria server and all Data Movers
3. Once installed, run the following command in your PostgreSQL logs folder (postgresqllogs) to detect the characteristic errors:

   Replace <path/to/miria> with the actual Miria installation directory on your system.

   Linux / macOS:

   grep -rE "could not access status of transaction|Could not open file.*pg_xact" <path/to/miria>/postgresqllogs/
   

   Windows (PowerShell):

   Get-ChildItem "<drive:\path\to\miria>\postgresqllogs\" -Recurse -Filter "*.log" | Select-String -Pattern "could not access status of transaction|Could not open file.*pg_xact"
   

4. If the command returns any results, open a support ticket with Atempo — our L2 team will assist you with the database reconstruction

If the command returns no results, no further action is required beyond applying the patch.

Credit

This issue originates from the PostgreSQL database engine. Atempo thanks the PostgreSQL Global Development Group for identifying and fixing the underlying defect. [PostgreSQL]

For any questions, contact Atempo support at https://support.atempo.com.