for sizing of our systems we use very often a load tests and we noticed, that hydra tables become very large if we don’t remove data. We speak mostly about these tables:
Known way to do some housekeeping is by using of /oauth2/flush. But it handles only hydra_oauth2_access table.
In the issue https://github.com/ory/hydra/issues/1574 aeneasr wrote on 13 August
Clean up should now be more or less automatic for most flows. We also introduced better foreign key checks since then. There might still be stale data but it definitely shouldn’t be too much. If you do find leaky tables in the latest version, please do report here
This is why we thought after upgrade to 1.7.4 the cleaning will work automatically. But I see with this version we have the same problem as before. /oauth2/flush handles only hydra_oauth2_access. Did I misunderstand that?
I can imagine cleaning e.g. hydra_oauth2_refresh after 30 days because our refresh token are valid for 30 days but what is about other tables?
Is there any official proper way to do some housekeeping considering all/most tables?
Thank you very much!