Potential error spikes with database patch

The issue has been resolved, and as a result, we were able to reenable the database operations that were temporarily disabled. The root cause was identified as a corrupted index, which caused database restarts when autovacuum was triggered. The corrupted index was rebuilt, resolving the issue and restoring autovacuum functionality.
We are still awaiting feedback from our cloud provider regarding the cause of the index corruption and will continue to monitor the situation. Thank you for your patience and understanding throughout this incident.

The service remains stable and fully operational, but the situation has not changed. We are still awaiting a response from our cloud provider. At the same time, we are investigating ways to safely reenable the database operations that were temporarily disabled to mitigate the issue. Thank you for your patience as we work towards a resolution.

The service remains stable, and we have taken additional measures to mitigate the issue, including adjustments to database operations that were impacting performance. We are continuing to work closely with our cloud infrastructure provider to address the root cause, which is not yet fully resolved.

The service remains stable, but we are continuing to monitor the situation and we are working with our cloud infrastructure provider for a long term solution.

We may still be experiencing some potential error spikes with the database maintenance patch that we had just performed. We're keeping to monitor and aim to resolve this fully.