Submitting a change was taking a long time to reach the next screen. It turned out that the getchangeinfo service was querying the MPE_AUDIT table, which had grown to 51gb
Adding an index to MPE_AUDIT fixed the problem
We also discovered that the mpe_checkrestore macro was not using dynamic audit values from MPE_TABLES
Submitting a change was taking a long time to reach the next screen. It turned out that the `getchangeinfo` service was querying the MPE_AUDIT table, which had grown to 51gb
Adding an index to MPE_AUDIT fixed the problem
We also discovered that the mpe_checkrestore macro was not using dynamic audit values from MPE_TABLES
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Submitting a change was taking a long time to reach the next screen. It turned out that the
getchangeinfoservice was querying the MPE_AUDIT table, which had grown to 51gbAdding an index to MPE_AUDIT fixed the problem
We also discovered that the mpe_checkrestore macro was not using dynamic audit values from MPE_TABLES