On Thu, Jul 29, 2021 at 02:19:17PM -0400, Álvaro Herrera wrote: > On 2021-Jul-29, Dave Cramer wrote: > > > > I suggest "can be upgraded" rather than "should be upgraded" because > > > we're not making a recommendation, merely stating the fact that it is > > > possible to do so. > > > > Why not recommend it? I was going to suggest that we actually run alter > > extension upgrade ... on all of them as a solution. > > > > What are the downsides to upgrading them all by default ? AFAIK if they > > need upgrading this should run all of the SQL scripts, if they don't then > > this should be a NO-OP. > > I'm not aware of any downsides, and I think it would be a good idea to > do so, but I also think that it would be good to sort out the docs > precisely (a backpatchable doc change, IMV) and once that is done we can > discuss how to improve pg_upgrade so that users no longer need to do > that (a non-backpatchable code change). Incremental improvements and > all that ...
Agreed. I don't think we have any consistent set of steps for detecting and upgrading extensions --- that needs a lot more research. -- Bruce Momjian <br...@momjian.us> https://momjian.us EDB https://enterprisedb.com If only the physical world exists, free will is an illusion.
