# Update took quite long due to Vacuum

**URL:** <https://meta.discourse.org/t/update-took-quite-long-due-to-vacuum/56203>\
**Category:** Self-hosting\
**Created:** [23. Januar 2017 um 11:37 UTC](https://meta.discourse.org/t/update-took-quite-long-due-to-vacuum/56203 "2017-01-23T11:37:15Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![rsoutar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rsoutar/32/121260_2.png) [@rsoutar](https://meta.discourse.org/u/rsoutar)\
**Post date:** [23. Januar 2017 um 11:37 UTC](https://meta.discourse.org/t/update-took-quite-long-due-to-vacuum/56203/1 "2017-01-23T11:37:16Z")

</div>

Hi, I was running an update using `./launcher rebuild app` But it stuck at

```
156:M 23 Jan 10:19:31.078 * 10 changes in 300 seconds. Saving...
156:M 23 Jan 10:19:31.081 * Background saving started by pid 3150
3150:C 23 Jan 10:19:31.655 * DB saved on disk
3150:C 23 Jan 10:19:31.657 * RDB: 26 MB of memory used by copy-on-write
156:M 23 Jan 10:19:31.714 * Background saving terminated with success
2017-01-23 11:23:52 UTC [3137-57] discourse@discourse WARNING: skipping "sql_languages" --- only table or database owner can vacuum it
2017-01-23 11:23:52 UTC [3137-58] discourse@discourse WARNING: skipping "sql_packages" --- only table or database owner can vacuum it
2017-01-23 11:23:52 UTC [3137-59] discourse@discourse WARNING: skipping "sql_parts" --- only table or database owner can vacuum it
2017-01-23 11:23:52 UTC [3137-60] discourse@discourse WARNING: skipping "sql_sizing" --- only table or database owner can vacuum it
2017-01-23 11:23:52 UTC [3137-61] discourse@discourse WARNING: skipping "sql_sizing_profiles" --- only table or database owner can vacuum it
WARNING: skipping "sql_languages" --- only table or database owner can vacuum it
WARNING: skipping "sql_packages" --- only table or database owner can vacuum it
WARNING: skipping "sql_parts" --- only table or database owner can vacuum it
WARNING: skipping "sql_sizing" --- only table or database owner can vacuum it
WARNING: skipping "sql_sizing_profiles" --- only table or database owner can vacuum it

```

Using htop I saw that it running a VACUUM for an hour or so.

 ![](https://global.discourse-cdn.com/meta/original/3X/9/6/965efc5337a9d0e1082576310bde17eefeffb19a.png)

Any ideas? Thank you

---

_[View the full topic](https://meta.discourse.org/t/update-took-quite-long-due-to-vacuum/56203)._