Select from pg_available_extensions shows installed_version 1.1, expected 1.1.1

[banlex73]

Hi there
Just installed the latest version from source
running select * from pg_available_extensions where name ='pg_wait_sampling'
name | default_version | installed_version | comment
------------------+-----------------+-------------------+------------------------------------------
pg_wait_sampling | 1.1 | 1.1 | sampling based statistics of wait events

Is it as expected? not 1.1.1 version?

[ololobus]

Hi @banlex73, yes it is expected. First two digits (*.*) are reserved for Postgres extension versioning. So they are incremented only if there were any changes in the extension SQL scripts, i.e. user-visible functions/schema.

The last digit (e.g. 1.1.*) is used to indicate only binary changes of the extension shared library. So it is only visible in GitHub releases and distro packages.

In the 1.1.1 release, for example, if we'd put 1.1.1 into pg_wait_sampling.control file, then we had to put an empty SQL upgrade script, so Postgres was able to upgrade from 1.1 to 1.1.1. Even if there were no changes in SQL.

This topic has been partially discussed here: #23 (comment)

Do you have any issues with this versioning scheme?

[banlex73]

Thank you Alexey for the explanation. No, I don't have any issues with versioning.. чт, 22 жовт. 2020 о 08:07 Alexey Kondratov <[email protected]> пише:

…

Hi @banlex73 <https://github.com/banlex73>, yes it is expected. First two digits (*.*) are reserved for Postgres extension versioning. So they are incremented only if there were any changes in the extension SQL scripts, i.e. user-visible functions/schema. The last digit (e.g. 1.1.*) is used to indicate only *binary* changes of the extension shared library. So it is only visible in GitHub releases and packages. In the 1.1.1 release, for example, if we'd put 1.1.1 into pg_wait_sampling.control file, then we had to put an empty SQL upgrade script, so Postgres was able to upgrade from 1.1 to 1.1.1. Even if there were no changes in SQL. This topic has been partially discussed here: #23 (comment) <#23 (comment)> Do you have any issues with this versioning scheme? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIHWEYGSFBYFWQ5YWCWK3PLSMBDBJANCNFSM4SSRBV3A> .

[ololobus]

OK, then I'm closing this issue. Feel free to open a new one if it's needed.