# 2.6.0 Beta4 update mislukt met wat lijkt op db-fouten

**URL:** <https://meta.discourse.org/t/2-6-0-beta4-update-failed-with-what-looks-like-db-errors/167661>\
**Category:** Self-hosting\
**Created:** [19 oktober 2020 om 19:20 UTC](https://meta.discourse.org/t/2-6-0-beta4-update-failed-with-what-looks-like-db-errors/167661 "2020-10-19T19:20:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Gunnar](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/gunnar/32/119647_2.png) [@Gunnar](https://meta.discourse.org/u/Gunnar)\
**Post date:** [19 oktober 2020 om 20:13 UTC](https://meta.discourse.org/t/2-6-0-beta4-update-failed-with-what-looks-like-db-errors/167661/3 "2020-10-19T20:13:10Z")

</div>

> [@Falco](#):
>
> That is a _very_ peculiar choice. Why not use RDS ?

Because I have zero idea how to even begin implementing that. It’s an interesting idea, though.

EFS is just a file system, so easy to implement. And fast enough for normal operations, at least for our use. Or, at least that’s what I thought.

> [@Falco](#):
>
> This happens when the container is not gracefully shutdown, so PostgreSQL will have to perform a recovery process on next start up.

Right, that’s what I thought. The interesting part is that when I fired up launcher, Discourse had been running for a while. So, it was the launcher script itself that shut down PostgreSQL.

> [@Falco](#):
>
> A simple recovery method is starting the container again with `./launcher start app` , letting it run happily for some time (let’s say 1h) and trying a rebuild later.

OK, I’ll try that. Thanks!

---

_[View the full topic](https://meta.discourse.org/t/2-6-0-beta4-update-failed-with-what-looks-like-db-errors/167661)._
