Bug fixes for problems (like slow queries) you didn't realize you had, or would have if you later implemented a feature with the bug. (For example, an aggravating weekly manual activity disappeared when I was allowed to update from 9.6.6 to 9.6.24.)
And, of course, security bug fixes, Won't you have egg on your face when it turns out that black hats stole data because of a bug fixed in a later release?
On Thu, Mar 7, 2024 at 10:49 AM David Gauthier <dfgpostgres@xxxxxxxxx> wrote:
Because 15.3 is the latest they have installed at this time. I could petition to get something even more recent. But it would only make sense if it's a significant win and not just options/features that we don't use.On Thu, Mar 7, 2024 at 12:53 AM Ron Johnson <ronljohnsonjr@xxxxxxxxx> wrote:On Wed, Mar 6, 2024 at 7:19 PM David Gauthier <dfgpostgres@xxxxxxxxx> wrote:Hi:I'm a PG user in a big corp with an IT dept that administers a PG server/instance that I use. It's an old install, v11.5, and we need to upgrade to v15.3. They want to bring the upgraded DB up on a new linux vm which has OS upgrades of its own. So it's a move AND an upgrade.Have them upgrade the current server to 11.22. It's trivially easy, with only a few minutes of down time.Remember (and tell your IT dept) that PG point releases do not add new features: only bug fixes. That means point releases aren't nearly as risky as other products.
