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

From Dave Cramer
Subject Re: pg_upgrade does not upgrade pg_stat_statements properly
Date
Msg-id CADK3HHLZdwJinfT0N9fDy8hUd-n1MUhOSOBFyotg00Mp2jXFQw@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade does not upgrade pg_stat_statements properly  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers


On Thu, 29 Jul 2021 at 00:35, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Wed, Jul 28, 2021 at 6:52 PM Bruce Momjian <bruce@momjian.us> wrote:
I came up with the attached patch.

Thank you.  It is an improvement but I think more could be done here (not exactly sure what - though removing the "copy binaries for contrib modules from the old server" seems like a decent second step.)

I'm not sure it really needs a parenthetical, and I personally dislike using "Consider" to start the sentence.

"Bringing extensions up to the newest version available on the new server can be done later using ALTER EXTENSION UPGRADE (after ensuring the correct binaries are installed)."


As for the patch. What exactly is being copied ? 
This is all very confusing. Some of the extensions will work perfectly fine on the new server without an upgrade. At least one of the extensions will appear to function perfectly fine with new binaries and old function definitions.
Seems to me we need to do more. 

Dave

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Replace l337sp34k in comments.
Next
From: Yura Sokolov
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum