Major version
A major version is the primary component of a version identifier that distinguishes a release line and commonly signals potentially backward-incompatible changes.
PostgreSQL Mistakes and How to Avoid Them
A major release is a PostgreSQL release that introduces substantial features and may change internal system-table or data-file formats.
- How it is used
- Frames major versions as planned operational upgrades requiring compatibility awareness, testing, and release-note review.
- How deep it goes
- Explains version-number roles, storage-format incompatibility, support, and a worked cross-version behavioral change without detailing upgrade commands.
- Examples
- Demonstrates a PostgreSQL 13-to-16 expiry-date change caused by fractional interval rounding introduced in PostgreSQL 15.
- What you can do after
- Evaluate/understand major-version upgrade risks by distinguishing data-format migration from subtle application behavior changes.
Read how PostgreSQL Mistakes and How to Avoid Them explains major version →
API Design Patterns
A major version is the first component of a semantic version that indicates a backward-incompatible change.
- How it is used
- Signals whether API consumers should expect existing code to remain compatible after a change.
- How deep it goes
- Defines the version component, contrasts it with minor versions, and applies it to field renaming and soft deletion.
- Examples
- Uses field renaming from 1.0.0 to 2.0.0 and adding a field from 1.0.0 to 1.1.0 as API examples.
- What you can do after
- Evaluate API changes and choose a major-version increment when compatibility is likely to break.
Related concepts
- semantic versioningpart of · Semantic Versioning is a version-numbering convention using MAJOR.MINOR.PATCH components to communicate compatibility impact: major for incompatible changes, minor for compatible additions, and patch for compatible fixes.
- breaking changeproduced by · A breaking change is a modification to an interface, behavior, format, configuration, or contract that can prevent existing consumers from working correctly without changes.
- versioningpart of · The practice of identifying and managing successive revisions of files, data, models, interfaces, or other artifacts so changes can be tracked and earlier states recovered.
- soft deletionconfigures · Soft deletion is a technique that marks or hides data as deleted while retaining its physical representation for recovery or later permanent removal.
- versionkind of · A version is a distinct, identifiable state or revision of an artifact, system, or product.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.