Version of currently installed postgis taken from wrong place ?

[strk]

When installing a PostGIS version with extensions disabled you end up with a NEW shared library (.so) but no new .control file for extension.

In this scenario, postgis_extensions_upgrade() will complan that you can NOT downgrade, thinking you're having the NEW version and attempting to bring you to the OLD version (from the .control file).

It sounds like the "OLD" version should be read from script-only, not from .so file, so this sounds like a bug to be fixed ASAP.

The guard against downgrade was introduced with [497e793493ccf96492665cbeab7482484e3f2a36/git] which was 3.3.0dev

[robe]

I'm a bit lost here. What are the steps to trigger this.

If you don't have the extension scripts installed for the new version, that sounds like a developer error to me. How can you be expected to upgrade without the latest scripts?

[robe]

Agree old version should be read strictly from postgis_scripts_installed()

[Sandro Santilli <strk@…>]

In 7dc3d5e7/git:

Use scripts_installed for downgrade protection

References #5329 in master branch (3.4.0dev)

[Sandro Santilli <strk@…>]

In 4b24856/git:

Use scripts_installed for downgrade protection

Closes #5329 in 3.3 branch (3.3.3dev)