Re: Managing major PostgreSQL upgrades - Mailing list pgsql-general

From Saul Perdomo
Subject Re: Managing major PostgreSQL upgrades
Date
Msg-id CAN3jBgF8B+tCM=8466NewDRFjEBikr7iJZmUYMU4W0SEc_F+Fg@mail.gmail.com
Whole thread Raw
In response to Managing major PostgreSQL upgrades  (Tiffany Thang <tiffanythang@gmail.com>)
Responses Re: Managing major PostgreSQL upgrades  (Tiffany Thang <tiffanythang@gmail.com>)
List pgsql-general
Hey Tiff, 

We're in a similar boat. We currently lean on (mostly custom) ansible scripting to automate all the repeatable tasks we can, but automation of major PG version upgrades is something we are yet to tackle -- although we plan to start this effort in the short term.

Would you mind sharing a bit more about your own current upgrade process? What's your standard, a dump+restore, a pg_upgrade, or replication-based? Also if you are able to share any lessons learned (e.g. common pitfalls you've run into) will all be useful information to identify ahead of time when drafting an automation strategy. 


On Mon., Nov. 15, 2021, 6:45 a.m. Tiffany Thang, <tiffanythang@gmail.com> wrote:
Hi,
Every year we spent a lot of time planning and manually performing major PostgreSQL upgrade on many of our on-prem and RDS instances. I’m wondering if there is a better way of managing these upgrades through automation. Can anyone share their experiences?

Thanks.

Tiff



pgsql-general by date:

Previous
From: Дмитрий Иванов
Date:
Subject: Re: pg_restore depending on user functions
Next
From: "Chen, Yan-Jack (NSB - CN/Hangzhou)"
Date:
Subject: RE: PostgreSQL debug log doesn't record whole procedure(from receiving request to sending response)