Hello @Jorge,
@zelterNN Is correct!
The the audit_trail_events table is safe to trim as needed.
As Linda mentioned in the thread that Zelter linked, she is correct.
The page_save holds all of every single time an app saves and can grow really big really fast.
If you clear it out, you will not be able to go back in a previous save.
Thus, the best option for trimming is to make a new release version of your app. Then when you join with the tags table, you can benchmark all the changes based on which tag(app version) the change corresponds to.
Then you can pick how far back in terms of app version you are ok with parting ways from and can then do the DB surgery to delete the save rows that are prior to the app version you want to keep!
Be careful with DB surgery as we recommend having a backup just in case anything unexpected happens so you can avoid the worse case scenario of losing a save or version of you app that you want to keep.
Hope this helps 