Re: pg_upgrade does not upgrade pg_stat_statements properly - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: pg_upgrade does not upgrade pg_stat_statements properly
Date
Msg-id CAKFQuwZWQf--+Gj7Ld9x+XQ_Bsvj+OE0_A01jj6GhQ451H4ZGA@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade does not upgrade pg_stat_statements properly  (Dave Cramer <davecramer@gmail.com>)
List pgsql-hackers
On Wed, Jul 14, 2021 at 12:21 PM Dave Cramer <davecramer@gmail.com> wrote:

On Wed, 14 Jul 2021 at 15:09, David G. Johnston <david.g.johnston@gmail.com> wrote:

Something like, "... because the installed extensions will be copied from the old cluster during the upgrade."

This is still rather opaque. Without intimate knowledge of what changes have occurred in each extension I have installed; how would I know what I have to fix after the upgrade. 

The point of this behavior is that you don't have to fix anything after an upgrade - so long as your current extension version works on the new cluster.  If you are upgrading in such a way that the current extension and new cluster are not compatible you need to not do that.  Upgrade instead to a lesser version where they are compatible.  Then upgrade your extension to its newer version, changing any required user code that such an upgrade requires, then upgrade the server again.

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Hooks at XactCommand level
Next
From: Tom Lane
Date:
Subject: Re: Replacing pg_depend PIN entries with a fixed range check