You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In one of our example apps, pg_boss filled up 1 GB of DB data without much usage.
The demo app was hosted on Supabase and we exceeded their free plan limits.
Upon investigation, I found ~500MB in the pg_boss.jobs table and ~500MB in the pg_boss.archive table. It seems that PgBoss keeps track of all executed scheduled jobs and their results. It also moves stuff to the archive table after some time.
We should investigate how this works exactly and offer our users a way to control the data retention time.
The text was updated successfully, but these errors were encountered:
In one of our example apps,
pg_boss
filled up 1 GB of DB data without much usage.The demo app was hosted on Supabase and we exceeded their free plan limits.
Upon investigation, I found ~500MB in the
pg_boss.jobs
table and ~500MB in thepg_boss.archive
table. It seems that PgBoss keeps track of all executed scheduled jobs and their results. It also moves stuff to the archive table after some time.We should investigate how this works exactly and offer our users a way to control the data retention time.
The text was updated successfully, but these errors were encountered: