From: Karl Denninger <karl@denninger.net>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Postgres open source upgrades
Date: Tue, 28 Jun 2022 17:07:58 -0400
Message-ID: <aaf9a36b-cfd0-8ab4-3bc7-b14aa8d5f60b@denninger.net> (raw)
In-Reply-To: <YrtgFX7Zu04ctk3e@momjian.us>
References: <6E89EC2B-D3EF-456A-A020-5A17D44F3103@gmail.com>
<YrtgFX7Zu04ctk3e@momjian.us>
On 6/28/2022 16:09, Bruce Momjian wrote:
> On Tue, Jun 28, 2022 at 12:13:11PM -0700, Teja Jakkidi wrote:
>> Hello pgsql-admin,
>>
>> I am very new to Postgres and trying to learn how upgrades work in Postgres.
>> We have open source installation and I am wondering if anyone can help me with correct documentation or steps on performing minor and major version upgrades.
> Please look here:
>
> https://www.postgresql.org/support/versioning/
>
> There are links to the documentation there.
To add to this from real-world experience over a /long /period of time
(I've been using this code since the 1990s!) with Postgres:
I've never had a minor version upgrade blow up in my face. Major
version upgrades require some care because if the "upgrade in place"
procedure is used and something goes wrong with it you can be in serious
trouble. It's supposed to check that but if it goes bad on you then I
hope you have a valid and recent backup as you can be in extremely
serious trouble if not/. Theoretically /the in-place process should
check first and refuse to proceed if there's a problem but if you
haven't met Mrs. Murphy I recommend thinking a long time before
proceeding with that in the absence of a mitigation strategy with data
you care about.
Exactly how you mitigate that risk requires some thought and much
depends on prior planning (the obvious is to not upgrade in-place and
thus the "pre-upgrade" copy, and the binaries, are still there in case
something goes wrong -- but that requires both the processing time and
disk storage for the second copy.)
--
Karl Denninger
karl@denninger.net
/The Market Ticker/
/[S/MIME encrypted email preferred]/
Attachments:
smime.p7s (application/pkcs7-signature, 4.8K) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: karl@denninger.net, pgsql-admin@lists.postgresql.org
Subject: Re: Postgres open source upgrades
In-Reply-To: <aaf9a36b-cfd0-8ab4-3bc7-b14aa8d5f60b@denninger.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox