Skip to content

Commit ad0db32

Browse files
committed
postGIS link update
1 parent 31a0c19 commit ad0db32

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/postgresql/migrate/best-practices-seamless-migration-single-to-flexible.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ The [postgres_fdw module](https://www.postgresql.org/docs/current/postgres-fdw.h
187187

188188
### Database with postGIS extension
189189

190-
The postgis extension has breaking changes/compat issues between different versions. Hence, the migration tool disallows migration if there is a version incompatibility. If you migrate to a Flexible server running PostgreSQL 11, this is not a problem, because FSPG11 supports same version of postGIS, which is available on Single server as well. So the migration goes ahead in this case. If you migrate to a Flexible server running PostgreSQL 12 or higher, the application should be checked against the changes in newer versions of postGIS to ensure that the application isn't impacted or the necessary changes have to be made to the Application. The [postGIS release notes page](https://postgis.net/news/) is a good starting point to understand the changes across versions. Once the changes are taken care of, raise a support request to allow-list migration for your Flexible server to a higher PostgreSQL version.
190+
The postgis extension has breaking changes/compat issues between different versions. Hence, the migration tool disallows migration if there is a version incompatibility. If you migrate to a Flexible server running PostgreSQL 11, this is not a problem, because FSPG11 supports same version of postGIS, which is available on Single server as well. So the migration goes ahead in this case. If you migrate to a Flexible server running PostgreSQL 12 or higher, the application should be checked against the changes in newer versions of postGIS to ensure that the application isn't impacted or the necessary changes have to be made to the Application. The [postGIS news](https://postgis.net/news/) and [release notes](https://postgis.net/docs/release_notes.html#idm45191) are a good starting point to understand the breaking changes across versions. Once the changes are taken care of, raise a support request to allow-list migration for your Flexible server to a higher PostgreSQL version.
191191

192192
### Database connection clean-up
193193

0 commit comments

Comments
 (0)