Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Query used for Schema Change Tracking causes high CPU usage



The query which is used in the Schema Change Tracking landing page is causing high CPU usage.

Error Messages

Not applicable

Steps to Reproduce

Go to the Schema Change Tracking landing page: Designer Studio > System > Database > Schema Change Tracking.

Root Cause

The query for Schema Change Tracking was causing a full table scan.

On Postgres database, it uses information_schema view which triggers un-needed joins.


Apply HFix-30016.


Suggest Edit

Published November 10, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us