In-place upgrade versus optional features
The second build of Windows Server vNext (based on Windows 11) came with an iso with installable optional features, via Dism. I plan to use in-place upgrade from build to build, not perform fresh installs on my test machine every time. I wonder if in-place upgrade shall be, practicly, blocked, if any of the optional features is installed, due to incompatibility between the installed optional features, on file/feature version number. Perhaps upgrade is possible, but optional features shall be uninstalled then, or kept, but needed to be reinstalled via Dism from new sources?PostgreSQL 17 General Availability with In-Place Upgrade Support
We’re excited to share that PostgreSQL 17 is now Generally Available on Azure Database for PostgreSQL – Flexible Server! This release brings community-driven enhancements including improved vacuum performance, smarter query planning, enhanced JSON functions, and dynamic logical replication. It also includes support for in-place major version upgrades, allowing customers to upgrade directly from PostgreSQL 11–16 to 17 without needing to migrate data or change connection strings. PostgreSQL 17 is now the default version for new server creations and major version upgrades. 📖 Read the full blog post: http://aka.ms/PG17 Let us know if you have feedback or questions!
