> This change also makes it easier for extensions that use versioned .so files > (by that I mean uses extension-<version>.so rather than extension.so). > Because such extensions can't really use the chaining property of the > existing upgrade system and so need to write a direct X--Y.sql migration file > for > every prior version X. I know the system wasn't designed for this, but in > reality a lot of extensions do this. Especially the more complex ones.
> Hopefully this is helpful, > Mat Thanks for the feedback. Yes this idea of versioned .so is also one of the reasons why we always have to run a replace on all functions. Like for example on PostGIS side, we have option of full minor (so the lib could be postgis-3.3.so or postgis-3.so) For development I always include the minor version and the windows interim builds I build against our master branch has the minor. But the idea is someone can upgrade to stable version, so the script needs to always have the .so version in it to account for this shifting of options. Thanks, Regina
