# PostgreSQL 15 update

**URL:** <https://meta.discourse.org/t/postgresql-15-update/349515>\
**Category:** Announcements\
**Created:** [January 29, 2025, 7:20am UTC](https://meta.discourse.org/t/postgresql-15-update/349515 "2025-01-29T07:20:00Z")\
**Posts on this page:** 1\
**Showing post:** 74

<div class="post-metadata">

**Author:** ![mwaniki](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mwaniki/32/313097_2.png) [@mwaniki](https://meta.discourse.org/u/mwaniki)\
**Post date:** [February 4, 2025, 5:56am UTC](https://meta.discourse.org/t/postgresql-15-update/349515/74 "2025-02-04T05:56:06Z")

</div>

> [@schneeland](#):
>
> Manually stopping the services inside the container apparently did the trick

Glad to hear that worked! I’ve now included those steps in [OP](https://meta.discourse.org/t/postgresql-15-update/349515#p-1698209-the-source-cluster-was-not-shut-down-cleanly-10).

On the high `postgres` CPU load on startup, it sounds like you’ve been experiencing the same issue even before the PG version update. If so, that’s unrelated to the update. (Regardless, it’s recommended to run a [vacuum](https://www.postgresql.org/docs/15/app-vacuumdb.html) after a PG version update. See the [post-update tasks](https://meta.discourse.org/t/postgresql-15-update/349515#p-1698209-post-update-optional-tasks-6).)

Poor database/query performance could be caused by a myriad of issues. It could be corrupt indexes in the database, an under-provisioned host, a bug in Discourse which introduced a problematic query etc. It might help to open a #Support topic for that.

---

_[View the full topic](https://meta.discourse.org/t/postgresql-15-update/349515)._