Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi 👋
I have rather small, hobbystic project that uses your gem. I've been checking which tables are the biggest among my project, and noticed this:
For my amount of rows (given how simple single row is)
I started investigating what exactly takes that much space.
It seems that
que_scheduler_audit
have bothPRIMARY KEY
constraint index ANDUNIQUE
index on the same column, meaning that the latter one is essentially redundant, thus I created a PR that drops it.After that change, I saved 18MB in my simple application: