# PostgreSQL 18 update for self-hosters

**URL:** https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194
**Category:** Announcements
**Created:** [August 3, 2026, 4:36am UTC](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194 "2026-08-03T04:36:42Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![chrisr](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisr/32/246622_2.png) [@chrisr](https://meta.discourse.org/u/chrisr)
#### Post date: [August 3, 2026, 7:56am UTC](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/9 "2026-08-03T07:56:52Z")

</div>

> [@one1](#):
>
> Can you give any specifics on what very large means?

> [@merefield](#):
>
> I read this as needing 3x the size of your database spare, whatever the size?

Apologies, that warning was poorly worded and incorrect.

In addition to the existing DB on disk you’ll need enough free space for the dump output and the new copy of the DB as it’s restored. pg\_dump’s output is usually smaller than the DB data directory, so 2x the current DB in free space should be enough. I’ll get this corrected in the upgrade script.

EDIT: The free space check has now been updated to look for 2x DB size instead of 3x.

---

_[View the full topic](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194)._