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

vacuum sqlite after pruning data #2697

Merged
merged 3 commits into from
Feb 27, 2025
Merged

vacuum sqlite after pruning data #2697

merged 3 commits into from
Feb 27, 2025

Conversation

imabdulbasit
Copy link
Contributor

No description provided.

{
let mut conn = self.pool().acquire().await?;
query("VACUUM").execute(conn.as_mut()).await?;
conn.close().await?;
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

think this get closed after drop but I am not sure

@imabdulbasit imabdulbasit merged commit 06c7f62 into main Feb 27, 2025
51 checks passed
@imabdulbasit imabdulbasit deleted the ab/vacuum-sqlite branch February 27, 2025 23:35
rob-maron pushed a commit that referenced this pull request Feb 28, 2025
* vaccum sqlite database

* use pruned height table for opening sqlite write txn

* move vacuum after each batch delete
sveitser pushed a commit that referenced this pull request Mar 7, 2025
* Init new file and a couple of setup lines

* working test for QC init case

* new test passing

* minimal third test

* complete test

* remove unused code

* test negative case

* move the view to use node 2 as the leaderg

* remove dead code

* receive instead

* disambiguate a couple of lines, remove commented out code

* grammar

* Fix tests

* improve test correctness

* remove duplication in expression

* fix naming

* permute ordering 6 ways

* clarify comment

* fix doc comment

* fix failing case, remove unsafe code

* add a comment

* fix names
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants