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 CAKFQuwZhCVAhsjBX7vnBxAkK1XvzHci=J_-ibZyLpNtrt2fMcg@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>)
Responses Re: pg_upgrade does not upgrade pg_stat_statements properly  (Dave Cramer <davecramer@gmail.com>)
Re: pg_upgrade does not upgrade pg_stat_statements properly  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Thursday, July 15, 2021, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Thursday, July 15, 2021, Dave Cramer <davecramer@gmail.com> wrote:

      Install any custom shared object files (or DLLs) used by the old cluster
      into the new cluster, e.g., <filename>pgcrypto.so</filename>,
      whether they are from <filename>contrib</filename>
-     or some other source.
However it may be
+     necessary to recreate the extension on the new server after the upgrade
+     to ensure compatibility with the new library.
      

 My uncertainty revolves around core extensions since it seems odd to tell the user to overwrite them with versions from an older version of PostgreSQL.

Ok. Just re-read the docs a third time…no uncertainty regarding contrib now…following the first part of the instructions means that before one could re-run create extension they would need to restore the original contrib library files to avoid the new extension code using the old library.  So that whole part about recreation is inconsistent with the existing unchanged text.

David J.

pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly
Next
From: "David G. Johnston"
Date:
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly