Rodrigo Rosenfeld Rosas

I joined a new project 4 months ago. While investigating a slow query I noticed that even after creating a new covering index the query planner would refuse to use it. We were running Postgres 15 and I decided to try Postgres 17 and confirmed it would use the covering index as expected which significantly improved the query performance. The follower database upgrade issue Next step was to push for the Postgres 15 to 17 upgrade, which seemed pretty straightforward according to this post from Heroku. So I gave it a try last Sunday in our staging database and noticed 2 things: The sign-in page downtime was about 3 minutes. Other parts of the application were down for much longer. .