# Trouble upgrading PostgreSQL from 9.3 to current

**URL:** <https://meta.discourse.org/t/trouble-upgrading-postgresql-from-9-3-to-current/49207>\
**Category:** Self-hosting\
**Created:** [August 25, 2016, 4:35pm UTC](https://meta.discourse.org/t/trouble-upgrading-postgresql-from-9-3-to-current/49207 "2016-08-25T16:35:27Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [August 28, 2016, 9:59pm UTC](https://meta.discourse.org/t/trouble-upgrading-postgresql-from-9-3-to-current/49207/10 "2016-08-28T21:59:31Z")

</div>

If you’re OK with some downtime, then this should work:

1. Take and download backup
2. `./launcher stop app`
3. `docker rm app`
4. `mv shared/standalone shared/standalone.9.3`
5. Edit `containers/app.yml` to change the `postgres.9.3` to `postgres`
6. `./launcher bootstrap app; ./launcher start app`
7. Import the backup

Step 4 is the step that “makes the current container cease to exist” in a meaningful sense. `shared/app` is where all of the PostgreSQL data, logs, etc live. By renaming it, rather than just deleting it, you’re leaving yourself with a fallback plan if the unexepected happens and everything goes to hell.

---

_[View the full topic](https://meta.discourse.org/t/trouble-upgrading-postgresql-from-9-3-to-current/49207)._