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

<div class="post-metadata">

**Author:** ![Tobias\_1](https://avatars.discourse-cdn.com/v4/letter/t/9dc877/32.png) [@Tobias\_1](https://meta.discourse.org/u/Tobias_1)\
**Post date:** [August 6, 2026, 1:15pm UTC](https://meta.discourse.org/t/postgresql-18-update-for-self-hosters/406194/45 "2026-08-06T13:15:56Z")

</div>

I received the following error message during the update:

```plaintext
Stopping PostgreSQL 15 database server:
main.Stopping PostgreSQL 18 database server:
mainError: The cluster is owned by group id 993 which does not exist ... failed!
failed!

```

The trick to fix this was to remove the old upgrade remnants and correct the permissions:

```plaintext
rm -rf /var/discourse/shared/standalone/postgres_data_new
chown -R 999:999 /var/discourse/shared/standalone/postgres_data

```

… Then run `./launcher rebuild app` twice, and optionally (if the migration succeeded and everything is running) `./launcher cleanup`.

Hope this helps. 🙂

---

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