Re: update to 16.2

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Matthias Apitz <guru(at)unixarea(dot)de>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: update to 16.2
Date: 2024-03-08 08:56:16
Message-ID: B6D8F675-8BB7-4DD3-B325-C2C4F776C6D9@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> On Mar 8, 2024, at 00:53, Matthias Apitz <guru(at)unixarea(dot)de> wrote:
> It does not say definitely that for all other versions a dump/restore is
> required.

You cannot just replace the binaries to upgrade from an earlier major version to 16.X. The release notes use "a dump/restore (is/is not) required" to indicated whether you can just replace the binaries ("is not") and restart the server on the same database files.

Dump/restore is not the only option for a major version upgrade. You can use the pg_upgrade utility that is part of the standard distribution, or logical replication to a new server on the new version.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Gustafsson 2024-03-08 08:58:36 Re: update to 16.2
Previous Message Matthias Apitz 2024-03-08 08:53:41 update to 16.2