# שדרוג האתר דורש עדכון בסיס נתונים לאחר עדכון ידני של בסיס הנתונים
**URL:** https://meta.discourse.org/t/site-upgrade-insisting-on-database-upgrade-after-manual-db-upgrade/356518
**Category:** Support
**Created:** [9 במרץ, 2025, 10:54pm UTC](https://meta.discourse.org/t/site-upgrade-insisting-on-database-upgrade-after-manual-db-upgrade/356518 "2025-03-09T22:54:13Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@CT075](https://meta.discourse.org/u/CT075)
#### Post date: [9 במרץ, 2025, 10:54pm UTC](https://meta.discourse.org/t/site-upgrade-insisting-on-database-upgrade-after-manual-db-upgrade/356518/1 "2025-03-09T22:54:13Z")
Hello,
I tried to perform a manual postgres upgrade according to the topic [here](https://meta.discourse.org/t/postgresql-15-update/349515). Everything went smoothly except the final rebuild step, where the launcher continues to inform me that I need to upgrade my database to postgres 15 (which I don’t have the disk space for). How can I debug this?
I am confident in my bash skills, so no need to hold back on running complicated commands.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 במרץ, 2025, 12:51am UTC](https://meta.discourse.org/t/site-upgrade-insisting-on-database-upgrade-after-manual-db-upgrade/356518/3 "2025-03-10T00:51:01Z")
You can change to the pg13 template and delay the upgrade.
What I would recommend is moving to a new vm, as your old one is probably out of date anyway.
Then you just restore the database to the new server. You can see [Move a Discourse site to another VPS with rsync](https://meta.discourse.org/t/move-a-discourse-site-to-another-vps-with-rsync/43812) and copy over the certificates. But don’t copy the database;it’s easier to restore it to the new server and skip the upgrade step.
---
### Author:  [@mwaniki](https://meta.discourse.org/u/mwaniki)
#### Post date: [10 במרץ, 2025, 9:18am UTC](https://meta.discourse.org/t/site-upgrade-insisting-on-database-upgrade-after-manual-db-upgrade/356518/4 "2025-03-10T09:18:57Z")
From your post, I presume you saw this message:
>
If so, the upgrade script still [detects](https://github.com/discourse/discourse_docker/blob/e42fa9711e9a8b27e9618342b5b456d3ba5b8025/templates/postgres.template.yml#L93) that you have PG 13 installed, which implies the old data directory is still being mounted in the container. Assuming the upgrade was successful, it’s possible the directories were not renamed correctly.
Keep in mind that `launcher` also checks for available disk space, but that returns a [different message](https://github.com/discourse/discourse_docker/blob/e42fa9711e9a8b27e9618342b5b456d3ba5b8025/launcher#L275).
If you’re still stuck, share your sanitized `app.yml` file, all the commands you ran for the manual upgrade and their outputs, and the full output from the rebuild.