We’ve talked through this further with the upstream and the Store team. The Store team is understandably concerned that having patch version tracks (e.g. 9.4.19) for PostgreSQL, which changes between patch versions in a way that requires sysadmin handholding, will set a precedent that tracks could be used for every version of any application. As well, any update to a track would cause the services installed by that snap to restart immediately.
We’ve agreed with @iliv to move back to major.minor tracks for now, and work with the Store team next week to develop a longer term plan such that this snap could be used in production environments. Meanwhile, we’ll also change the description to warn that updates to a track will cause services to restart and thus this snap should only be used in dev and test environments.
So, let’s move to 11.0, 10.5, 9.6, 9.5, 9.4, and 9.3 for the track names. We’ll use
snapcraft release to move the revision for 9.4.19 into 9.4 and so on.