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

Fix size calculation in --optimize vacuum (bp #1447) #1451

Merged
merged 3 commits into from
Mar 17, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Mar 17, 2021

This is an automatic backport of pull request #1447 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.io/

The database size was still trying to stat a filesystem path as used
by SQLite as the database name.
This is changed to use the SQL function pg_database_size instead and
also the case where the size increases is now handled.

(cherry picked from commit b1d80a8)
In the "vacuum" case, old_size and new_size no longer need to be
initialized with 0.

(cherry picked from commit b4d48f7)
@mergify mergify bot requested a review from a team as a code owner March 17, 2021 12:40
@timopollmeier timopollmeier merged commit 9375764 into gvmd-21.04 Mar 17, 2021
@timopollmeier timopollmeier deleted the mergify/bp/gvmd-21.04/pr-1447 branch March 17, 2021 13:10
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.

1 participant