# Upgrade Postgres with REALLY limited space

**URL:** <https://meta.discourse.org/t/upgrade-postgres-with-really-limited-space/201937>\
**Category:** Self-hosting\
**Tags:** server-resources\
**Created:** [August 27, 2021, 5:42pm UTC](https://meta.discourse.org/t/upgrade-postgres-with-really-limited-space/201937 "2021-08-27T17:42:10Z")\
**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:** [February 13, 2022, 8:24pm UTC](https://meta.discourse.org/t/upgrade-postgres-with-really-limited-space/201937/14 "2022-02-13T20:24:52Z")

</div>

Hmm. Could be a wash. I think with the backup model one of the copies is compressed,which could make a difference? And the site that I did it on had backups on S3. And it was a test site so the stakes were low if there was a problem.

> [@Wingtip](#):
>
> Deleting the DB and restoring the backup sounds pretty risky.

Except backups are used lots more often in lots more situations than the upgrade in place. I consider it much safer.

---

_[View the full topic](https://meta.discourse.org/t/upgrade-postgres-with-really-limited-space/201937)._