Full disk may cause unexpected database restart

Detail name	Value
Changelog Number	11015
Type	Bug
Status	Open
Affected Versions

Background

If many sessions consume a lot of temporary memory a full disk event can be triggered.
To handle this, the database identifies the session with the highest memory consumption and terminates it to avoid a complete restart of the database.

Description

In some cases, the full disk event cannot be managed in time, causing an unexpected database restart.

Workaround

There is no workaround. After the automatic restart, the database is available again.

Fix

Database stays online in these cases.