supports minor version upgrades and major engine version upgrades, which differ in scope, compatibility, and business impact.
|
Comparison item |
Minor version upgrade |
Major engine version upgrade |
|
Version number change |
Patch version number changes only, such as |
Major kernel version changes, such as |
|
Upgrade content |
Kernel bug fixes, security patches, stability improvements, and performance optimizations. Typically no new features. |
New features, syntax, architectural improvements, or behavior changes such as index format, WAL format, or system view changes. |
|
Compatibility |
Fully backward compatible. No application changes required. |
May include incompatible changes. Test SQL behavior, extension support, and parameter settings before upgrading. |
|
Upgrade method |
Online rolling upgrade with a brief disconnection (seconds). No data migration required. |
Requires data migration through a service such as DTS. Complex and time-consuming. |
|
Trigger methods |
Typically triggered manually. For important security vulnerabilities, the system may initiate a mandatory upgrade during your maintenance window. |
Not triggered automatically. You must plan, initiate, and fully validate the upgrade. |
|
Rollback capability |
Supports fast rollback. |
Supported, but requires manual switchover to the original cluster. |