---
title: "Discussion on \"How We Fixed Aurora PostgreSQL Upgrade (13.* → 15.* → 17.*) Issues Caused by PostGIS\" | Hashnode"
description: "Discussion on \"How We Fixed Aurora PostgreSQL Upgrade (13.* → 15.* → 17.*) Issues Caused by PostGIS\". Upgrading Aurora PostgreSQL can sometimes feel like navigating a minefield, especially when extensions like PostGIS are involved. Here’s a real-world example of how we resolved an upgrade from PostgreSQL 13.20 → 15.12 → 17.4 that was blocked by PostG..."
url: "https://hashnode.com/posts/how-we-fixed-aurora-postgresql-upgrade-issues-caused-by-postgis/69677341ceb6697cb6e262ba"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How We Fixed Aurora PostgreSQL Upgrade (13.\* → 15.\* → 17.\*) Issues Caused by PostGIS](https://jshims.hashnode.dev/how-we-fixed-aurora-postgresql-upgrade-issues-caused-by-postgis?utm_source=hashnode&utm_medium=feed)

Upgrading Aurora PostgreSQL can sometimes feel like navigating a minefield, especially when extensions like PostGIS are involved. Here’s a real-world example of how we resolved an upgrade from PostgreSQL 13.20 → 15.12 → 17.4 that was blocked by PostG...

Jan 14 · 4 min read · jshims.hashnode.dev  
Read the article

-   [#aws](https://hashnode.com/tag/aws)
-   [#aws-aurora](https://hashnode.com/tag/aws-aurora)
-   [#postgresql](https://hashnode.com/tag/postgresql)

## Written by

[JaeHyun Shim](https://hashnode.com/@jshims)

@jshims · Seoul, Korea

  
[View profile](https://hashnode.com/@jshims)

Software Developer @RSquare

## Responses

Markdown supported · ⌘↵ to post

No responses yet.