Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate how to better control pg_boss DB usage #2313

Open
infomiho opened this issue Oct 1, 2024 · 0 comments
Open

Investigate how to better control pg_boss DB usage #2313

infomiho opened this issue Oct 1, 2024 · 0 comments
Labels
jobs shouldfix We should do/fix this at some point

Comments

@infomiho
Copy link
Contributor

infomiho commented Oct 1, 2024

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.

@infomiho infomiho added the jobs label Oct 1, 2024
@Martinsos Martinsos added the shouldfix We should do/fix this at some point label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
jobs shouldfix We should do/fix this at some point
Projects
None yet
Development

No branches or pull requests

2 participants