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 CAKFQuwYde-GKV0CrRUZMVefKFPbF-Tb8JjaRUjDf+MxXT89xyg@mail.gmail.com
Whole thread Raw
In response to Re: pg_upgrade does not upgrade pg_stat_statements properly  (Jan Wieck <jan@wi3ck.info>)
List pgsql-hackers
On Thursday, July 15, 2021, Jan Wieck <jan@wi3ck.info> wrote:
On 7/15/21 4:24 PM, David G. Johnston wrote:

OK, especially as this seems useful outside of pg_upgrade, and if done separately is something pg_upgrade could just run as part of its new cluster evaluation scripts.  Knowing whether an extension is outdated doesn't require the old cluster.

Knowing that (the extension is outdated) exactly how? Can you give us an example query, maybe a few SQL snippets explaining what exactly you are talking about? Because at this point you completely lost me.

I was mostly going off other people saying it was possible.  In any case, looking at pg_available_extension_versions, once you figure out how to order by the version text column, would let you check if any installed extensions are not their latest version.

David J.

pgsql-hackers by date:

Previous
From: Jan Wieck
Date:
Subject: Re: pg_upgrade does not upgrade pg_stat_statements properly
Next
From: "r.takahashi_2@fujitsu.com"
Date:
Subject: RE: Speed up COMMIT PREPARED