# Postgres Schema Upgrade

**URL:** <https://community.temporal.io/t/postgres-schema-upgrade/10761>\
**Category:** Server Deployment\
**Created:** [January 23, 2024, 10:54am UTC](https://community.temporal.io/t/postgres-schema-upgrade/10761 "2024-01-23T10:54:25Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![craigd](https://sea2.discourse-cdn.com/flex016/user_avatar/community.temporal.io/craigd/32/3166_2.png) [@craigd](https://community.temporal.io/u/craigd)\
**Post date:** [January 23, 2024, 10:54am UTC](https://community.temporal.io/t/postgres-schema-upgrade/10761/1 "2024-01-23T10:54:25Z")

</div>

My understanding of the documentation at [Upgrade the Temporal Server | Temporal Documentation](https://docs.temporal.io/self-hosted-guide/upgrade-server) is that if you are using ES for advanced visibility there is no need to upgrade the Postgres SQL DB schema.

The example shows using the `v96` schema for the default persistence store and the document states _“if you’re upgrading PostgreSQL to v12 or later to enable advanced Visibility features with Temporal Server v1.20, upgrade your PostgreSQL version first, and then run `temporal-sql-tool` with the `postgres12` plugin”_

Are there any benefits from upgrading the Temporal default persistence store to `v12`? We are already running Temporal 1.22? Was the action to simply upgrade using the `v96` schema the correct one?

Thanks.