That second bullet is significant for anyone who has a Persistent TCP publisher doing history syncs running on an H2 database. This was found to be the main culprit finally in relatively simple systems having databases grow into the gigabytes, but not having any events to speak of. We also raised the underlying issue with the H2 developers, and it is likely to have some patch soon for the larger issue of why all that space gets taken.
