# Problem rebuilding because of slow database shutdown

**URL:** https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366
**Category:** Self-hosting
**Created:** [April 19, 2023, 6:36pm UTC](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366 "2023-04-19T18:36:27Z")
**Posts on this page:** 1
**Showing post:** 14

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [April 20, 2023, 2:38pm UTC](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366/14 "2023-04-20T14:38:31Z")

</div>

> [@Wingtip](#):
>
> is the switching method documented?

You can check out [Move from standalone container to separate web and data containers](https://meta.discourse.org/t/move-from-standalone-container-to-separate-web-and-data-containers/29413)

> [@Wingtip](#):
>
> And are there any other advantages that increasing the 60s timer wouldn’t provide?

You can build a new container while the old one continues to run. You don’t need to shut down the database to build a new container.

> [@Wingtip](#):
>
> So any advantages for us at all?

There is now a 10 minute window for shutting down postgres, which should solve your current problem. Once you do one more rebuild, you’ll have the 10 minutes instead of one.

---

_[View the full topic](https://meta.discourse.org/t/problem-rebuilding-because-of-slow-database-shutdown/262366)._