A minor release is a PostgreSQL update that fixes bugs, security issues, and data-corruption problems without adding features or changing internal data formats. Minor releases arrive roughly quarterly and occupy the final part of the version number, such as 16.4. section 7.6
Treating a stable system as a reason to postpone minor upgrades is risky: latent bugs, new security vulnerabilities, changing workloads, and unexpected data-access patterns can expose problems later. The PostgreSQL community considers skipping these updates riskier than installing them. section 7.6 section 7.8
Keep the versioning distinction clear:
- Use the final version component to identify a minor release, as in 16.4. section 7.6
- Expect no new features or internal-format changes from a minor release. section 7.6
- Distinguish major releases, which add thoroughly vetted features and may change system-table and data-file formats. section 7.6
The tempting “it works fine” decision
A team leaves its PostgreSQL installation unchanged because testing and monitoring show no current failures. That decision can still leave known bugs or security vulnerabilities unaddressed. Installing the appropriate minor release preserves the internal format while reducing those risks; avoiding it can produce the very instability the team hoped to avoid. section 7.6 section 7.8
