RE: Upgrade procedure - Mailing list pgsql-general

From Rich Shepard
Subject RE: Upgrade procedure
Date
Msg-id alpine.LNX.2.20.1911051007220.1807@salmo.appl-ecosys.com
Whole thread Raw
In response to RE: Upgrade procedure  (Kevin Brannen <KBrannen@efji.com>)
List pgsql-general
On Tue, 5 Nov 2019, Kevin Brannen wrote:

> The manual or others here are more knowledgeable than I, but I believe that
> for a "minor" upgrade, you can just swap out the code and restart PG. For
> major upgrades, the PG server is going to have to come down as the underlying
> files might be changed/transformed during the upgrade, ...

Files might change even with a minor upgrade. The few seconds it takes to
stop, upgrade, and restart the system prevents all errors due to
someone/something accessing the database while it's being upgraded.

Rich



pgsql-general by date:

Previous
From: Kevin Brannen
Date:
Subject: RE: Upgrade procedure
Next
From: rihad
Date:
Subject: Re: Upgrade procedure