Hi Everyone,

As part of this upcoming release we've upgraded the database version from postgresql 14 to 18

The impact of this is very similar to when we last upgraded the DB version.

As a consequence of this we require more DB space than would normally be the case as we have a high water mark of having both a 14 and 18 DB concurrently during the upgrade. Because of this, the upgrade will not proceed unless the filesystem containing the database has sufficient space available. The expected amount required during the upgrade is 1.5 times the existing database size, plus 10GB margin, is available.

The attached doc explains the logic behind the space requirements and the upgrade procedure itself, while the attached script allows you to run this in advance of any upgrade and it effectively performs the various checks described in the doc.

We hope these will allow you plan in advance for any potential impacts caused by the one off upgrade scenario

As usual, we welcome any feedback or questions on this topic.

------------------------------
Martin Feeney
Product Manager, IBM Security QRadar SOAR
martin.feeney@ie.ibm.com
------------------------------

Good heads-up from the QRadar SOAR team. The PostgreSQL 14 to 18 upgrade is a significant jump, and the temporary storage requirement is definitely something administrators should validate before starting the upgrade.

The provided pre-check script is especially useful here. Having at least 1.5× the existing database size plus a 10 GB margin available should be part of the upgrade readiness checklist.

Thanks for sharing this proactively, Martin.

------------------------------
Allan Solomon Mejia
------------------------------