How can increase in toast bytes of DB table pr_operators be explained?
Using PDC, I made a custom report to see why the pr_operators table on our production environment is so big. It contains around 60K records but takes a Total Bytes of around 21GB. I found that last month the Estimate Row Count and Live Rows did not increase that much, but the Toast Bytes increased a lot in 1 day.
Possible reason/related issue for this is that we have a lot of REST calls internally and that the service operator is saved almost constantly.
As Laurence has already posted it seems like this table has not be vacuumed recently. Every time an operator logs in the pr_operators table record for that operator will get updated with the last signed on time. If you have operators being used for things like soap or rest services you should look to shut off the update of pr_operators which would happen each time the service is invoked.
Is it possible to run the VACUUM statement on PegaCloud without support of GCS? I could create an RDB rule for this. Or should it be requested as a change request?
The vacuum details of the table: Last Analysis = okt 25 at 16:42 / Last Vacuum = okt 25 at 16:42 / Last Automatic Analysis = okt 28 at 01:11 / Last Autovacuum = okt 28 at 01:12.
We have an SR open for the issue with service operators saving all the time but we didn't receive a working solution (SR-D53165). Today we found a solution on PDN setting the extAssignFlag property avoiding the resave.