As part of our recent Continuous Testing upgrade (to 24.6), we enabled reporter's "JSON support" feature (https://docs.digital.ai/bundle/COM/page/reporter_-_support_for_json_in_postgresql.html), which migrated test data from one database structure to another.

In preparation for this change and the data migration, we also performed some data clean-up activities to remove outdated and irrelevant data. We analyzed the Continuous Testing databases to identify what was consuming space and to determine what data could be removed to reduce the overall size.

Based on our analysis, we have the following ideas:

1. Reporter DB - Old "Per Project" Tests Tables:
We observed that the "JSON support" feature migrates test result data from the "tests_X" tables, where X is the Project ID, to the "test_reports" table. However, after the migration, the "tests_X" tables (including their large indexing data) remain in the database. These tables appear to be unused but still occupy significant space. To address this, we reindexed some of these tables as their index data was consuming a lot of space.

Are there any plans to include the clean-up of these "per project" "tests_X" tables in future feature versions? If not, are there any recommendations or procedures we should follow to safely clean up these tables?

2. CloudServer DB - Old Sessions Data:
Additionally, we noticed that the CloudServer DB contains a large amount of old data related to historical sessions and device reservations. We are considering deleting or cleaning up some of this older data. Are there any functionalities or APIs available to assist with this? Alternatively, could you provide recommendations or procedures, such as SQL statements, for safely cleaning up this old data?

Comments

  • Thank you for your submission. This is planned as part of the roadmap. In the meantime, our support team can assist in performing a safe cleanup for on-premises installations.