:thread: self-hosted hydra DB clean-up `hydra jan...
# ory-selfhosting
b
đź§µ self-hosted hydra DB clean-up
hydra janitor
uses the DELETE command internally to clean up the table details. Based on my understanding, the delete command introduces gaps in the DB, which means it doesn’t free up space, leading to fragmentation: https://stackoverflow.com/questions/1940533/does-sqls-delete-statement-truly-delete-data. I want to understand, how people ensure this is not happening in the case of self-hosted Ory hydra. Any case study/references. github link: https://github.com/ory/hydra/discussions/3972
m
Hello @big-jewelry-76857 I answered here in your discussion: https://github.com/ory/hydra/discussions/3972#discussioncomment-12702651 Feel free to reach out to us and we can talk about your use case and how to best address it with the Ory Enterprise License. There are some technical nuances that need to be considered but generally the OEL is exactly what you are looking for here.
i
While not a case study or reference, I consider this article to be a pretty good starting point for postgresql: https://dev.to/timescale/optimize-postgresql-storage-what-developers-must-know-4pef Similar capabilities exist for other RDBMS