cron.job_run_details
I see some stats on these in reports > database, they seem to be the stored historical info about cron jobs that have run but where are they kept and how often are they "clearned out" or are they not "cleared out"?
GThey are not cleaned out. Citus recommends adding a clean out to that table... https://github.com/citusdata/pg_cron
Check the cron schema. There are only two tables.
Check the cron schema. There are only two tables.
GitHub
Run periodic jobs in PostgreSQL. Contribute to citusdata/pg_cron development by creating an account on GitHub.
Dso i have to run a cronjob, to clear out the cron jobs?
GLOL... Yes.
Dthere not used by SB for anything after the event?
GThat is not a SB extension and they don't use it internally as you have to install it (or use their cron UI to install it).
Dok, but its running in the db ye? i see user postgres, db postgres, so cant SB run a cron to clean these out across all accounts?
GThey could but they just give you the ability to use that company's extension (pretty much the main one for cron with Postgres). They also would have to know you have cron installed which is a Postgres operation that Supabase would not know if you ran with SQL or not... except if you used the UI.
GYou could certainly give them a feature request at supabase/supabase github discussions. They don't monitor here for the most part.
DGitHub
It would be good if supabase could do a "auto" clear out of the cron.job_run_details that a cron produces at some configuarble time etc, e.g. every day for the previous days and beyond on...
