# 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:** 10

<div class="post-metadata">

### Author: ![Ivan\_Rapekas](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ivan_rapekas/32/248924_2.png) [@Ivan\_Rapekas](https://meta.discourse.org/u/Ivan_Rapekas)
#### Post date: [August 3, 2026, 8:54am UTC](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/10 "2026-08-03T08:54:26Z")

</div>

Seems, on single-core VM it’s needed to stay on PG15 ` postgres.15.template.yml` due to limitation:

```plaintext
pg_dump: error: -j/--jobs must be in range 1..2147483647

```

or patch `web.template.yml` to `-j1` to use one CPU. (Next rebuild will return the default value).

Yes, such configurations exist! :blob_wave:

---

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