Question

6
Replies
270
Views
Maarten Veger (MaartenBPM)
BPM Company
Managing Consultant & Pega CLSA
BPM Company
NL
MaartenBPM Member since 2013 11 posts
BPM Company
Posted: October 28, 2019
Last activity: October 29, 2019
Posted: 28 Oct 2019 7:00 EDT
Last activity: 29 Oct 2019 11:55 EDT
Closed

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.


I've ready about TOAST https://www.postgresql.org/docs/9.5/storage-toast.html and https://wiki.postgresql.org/wiki/TOAST and the general idea about this, but I could use some more context here.


My questions:


- The Total Bytes (in PDC on class PegaAES-Data-DBTableUsage) is the sum of Table Bytes, Toast Bytes and Index Bytes. What are exactly Toast Bytes? How can you see more info on the space used for it?


- What could be reasons for the toast bytes to increase so much in a day, while the number of records is gradually increasing. Can this be explained by a lot of resaves of service operators?


- How can you decrease the Toast Bytes? It went from 13GB to 20GB and stayed like that;


- Is the Total Bytes representative for the RDS Disk Space that is used? When can it differ?



***Edited by Moderator Marissa to update platform capability tags****


***Moderator Edit-Vidyaranjan: Updated SR details***

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.

I've ready about TOAST https://www.postgresql.org/docs/9.5/storage-toast.html and https://wiki.postgresql.org/wiki/TOAST and the general idea about this, but I could use some more context here.

My questions:

- The Total Bytes (in PDC on class PegaAES-Data-DBTableUsage) is the sum of Table Bytes, Toast Bytes and Index Bytes. What are exactly Toast Bytes? How can you see more info on the space used for it?

- What could be reasons for the toast bytes to increase so much in a day, while the number of records is gradually increasing. Can this be explained by a lot of resaves of service operators?

- How can you decrease the Toast Bytes? It went from 13GB to 20GB and stayed like that;

- Is the Total Bytes representative for the RDS Disk Space that is used? When can it differ?

***Edited by Moderator Marissa to update platform capability tags****

***Moderator Edit-Vidyaranjan: Updated SR details***

Pega Predictive Diagnostic Cloud Data Integration Cloud Services Reporting Support Case Created
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.