Julian Markwort <julian.markwort@uni-muenster.de> writes:
> Andres Freund wrote on 2018-03-02:
>> and I'd checked that 1.5 already exists. But you just renamed the file,
>> presumably because it's essentially rewriting the whole file? I'm not
>> sure I'm a big fan of doing so, because that makes testing the upgrade
>> path more work.
> You're right about 1.5 already existing. I wasn't sure about the versioning policy for extensions and seeing as
version1.5 only changed a few grants I quasi reused 1.5 for my intentions.
Nope, that's totally wrong. You can get away with that if we've not
already shipped a 1.5 release --- but we did ship it in v10, so that
version is frozen now. You need to make your changes in a 1.5--1.6
upgrade file. Otherwise there's no clean path for existing installations
to upgrade to the new version.
regards, tom lane
