# Sonar upgrade from 9.X to 10.1 - sonar and postgres errors

**URL:** <https://community.sonarsource.com/t/sonar-upgrade-from-9-x-to-10-1-sonar-and-postgres-errors/112093>\
**Category:** SonarQube Server / Community Build\
**Created:** [March 26, 2024, 3:29pm UTC](https://community.sonarsource.com/t/sonar-upgrade-from-9-x-to-10-1-sonar-and-postgres-errors/112093 "2024-03-26T15:29:11Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![sub](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/sub/32/57407_2.png) [@sub](https://community.sonarsource.com/u/sub)\
**Post date:** [May 10, 2024, 7:40am UTC](https://community.sonarsource.com/t/sonar-upgrade-from-9-x-to-10-1-sonar-and-postgres-errors/112093/13 "2024-05-10T07:40:07Z")

</div>

Hey arun,

I had issues with [something similar](https://community.sonarsource.com/t/errors-from-sonarqube-10-1-0-community-onwards/114785).

My problem was an outdated Postgres image version. If it is not already, make sure to bring it up to version 15. As per docs, versions 11 to 15 should be supported.

Since you are using Docker, you are likely using volumes for the database’s persistance. Postgres won’t like them being created by an older version, so you’ll likely have to wipe them. To retain the data, a rough idea is to: dump → stop and remove containers → remove the volume → deploy new version → drop newly created tables → import the dump → redeploy.

All the best.

---

_[View the full topic](https://community.sonarsource.com/t/sonar-upgrade-from-9-x-to-10-1-sonar-and-postgres-errors/112093)._