There are not that many tables, 175.
There are a decent number of transactions on the database, 35k a second
during the day. I ran a vacuum verbose on table1 today and got this output
on the pages frozen.
frozen: 2813436 pages from table (0.70% of total) had 7028123 tuples frozen
On Fri, Jan 3
On Fri, Jan 31, 2025 at 5:28 PM Joshua Banton wrote:
> The issue mostly manifests near the end of the "scanning heap" phase of
> vacuuming of one of our largest tables, we'll call table1. RDS Performance
> Insights reports that selects on table1 start to wait on cpu, where
> previously it didn'
Hello,
We are experiencing a high system cpu issue with our database that we can't
quite explain.
Description of the issue:
The database instance cpu suddenly increases to over 90%, the majority of
it as reported by RDS Enhanced Monitoring being system cpu, as opposed to
coming from Postgres itse
