iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
PostgreSQL supports each major version for five years. A new major version usually arrives once a year, while bug-fix and security releases arrive at least quarterly. Minor upgrades normally involve replacing the server binaries and restarting; major upgrades require pg_upgrade or a dump-and-reload migration because the data directory is not backward-compatible between major versions.
How PostgreSQL version support works
The PostgreSQL Global Development Group maintains each major version for five years from its initial release. During that period, the project publishes minor releases containing bug fixes, security fixes, and data-corruption fixes. After the fifth anniversary, PostgreSQL publishes a final minor release and marks that major version end of life (EOL). An EOL version no longer receives community fixes, including fixes for newly discovered security problems.
The project recommends running the current minor release for your chosen major version rather than staying on an older patch. Emergency releases can be issued outside the normal calendar when a serious problem requires immediate attention.
Major and minor versions: what the numbers mean
PostgreSQL 10 and later
Since PostgreSQL 10, the first number identifies the major version and the second number identifies the minor release. For example, 17.10 is major version 17, minor release 10. A minor release does not represent a new feature generation; it is the maintained patch level of that major version.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Versions before PostgreSQL 10
Older releases used a different convention in which the first two components represented the major version and a third component represented the patch level. This matters when reading old inventory records, package names, backup documentation, or upgrade procedures: do not assume that every additional number means the same thing across PostgreSQL’s history.
Which PostgreSQL versions are supported now?
The current official support table lists PostgreSQL 14 through 18 as supported. The dates below are the project’s published first-release and final-release dates; the final date is the point at which that major version stops receiving fixes.
| Major version | Initial release | Planned final release and EOL | Planning implication |
|---|---|---|---|
| PostgreSQL 18 | September 25, 2025 | November 14, 2030 | Newest supported major; verify extension and operating-system availability before adopting. |
| PostgreSQL 17 | September 26, 2024 | November 8, 2029 | Long support runway for a migration target. |
| PostgreSQL 16 | September 14, 2023 | November 9, 2028 | Still supported with several years remaining. |
| PostgreSQL 15 | October 13, 2022 | November 11, 2027 | Supported, but schedule the next major migration rather than treating it as a long-term endpoint. |
| PostgreSQL 14 | September 30, 2021 | November 12, 2026 | Immediate upgrade planning priority because fixes stop on November 12, 2026. |
The May 14, 2026 release notice explicitly states that PostgreSQL 14 will stop receiving fixes on November 12, 2026. That notice also announced PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23. Those releases addressed 11 security vulnerabilities and more than 60 bugs. The counts describe that particular coordinated release event, not a typical number for every quarterly update.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When do new PostgreSQL releases arrive?
Annual major releases
PostgreSQL targets one new major version about once a year, generally around September. PostgreSQL 18 was released on September 25, 2025. A new major version introduces features and may change internal behavior, planner results, defaults, and compatibility requirements, so it should be treated as a migration project rather than a routine patch.
Quarterly minor releases
The roadmap targets minor releases on the second Thursday of February, May, August, and November. The official FAQ describes patch releases as quarterly, while the versioning policy says each major version receives a minor release at least once every three months. Urgent security or reliability issues can produce an additional release between those dates.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
The PostgreSQL 19 planning date
The project roadmap lists PostgreSQL 19 as planned for October 2026. A roadmap date is not a release announcement: use it for capacity and testing plans, then confirm the final announcement before selecting PostgreSQL 19 for production. A target that slips by weeks can affect extension packages, operating-system repositories, and your maintenance window.
Major versus minor upgrades
| Characteristic | Minor upgrade | Major upgrade |
|---|---|---|
| Example | 17.9 to 17.10 | 16 to 17 |
| Purpose | Bug, security, and data-corruption fixes; low-risk corrections | New features and major-version behavior or compatibility changes |
| Data-directory compatibility | Maintained within the major version | Not backward-compatible between major versions |
| Normal method | Stop PostgreSQL, install new binaries, restart | pg_upgrade or dump and reload |
| Dump/reload normally required? | No, unless release notes require an exceptional procedure | Yes, either directly through pg_upgrade or logically through dump and reload |
| Typical scheduling | Short maintenance window, after checking release notes | Planned migration with testing, cutover, validation, and rollback criteria |
For a minor release, the normal sequence is to stop the server, replace the binaries with the newer packages, and start PostgreSQL again. The cluster data remains in place. Always read that release’s notes first because an exceptional fix can require an extra action.
For a major release, PostgreSQL cannot maintain the old data directory in backward-compatible form. You must either use pg_upgrade, which converts a cluster in a controlled migration, or create logical dumps and restore them into a newly initialized cluster. A direct jump can skip intervening major versions, but administrators should read the release notes for every intervening version so that changes to authentication, settings, extensions, replication, and SQL behavior are not missed.
A practical PostgreSQL upgrade-planning workflow
1. Build a complete inventory
List every PostgreSQL server and cluster, not just the primary production instance. Record the exact major and minor version, operating system and package source, data directory location, extensions and their versions, client drivers, connection pools, replication topology, backup tooling, and dependent applications. Include reporting replicas, development environments, disaster-recovery clusters, and managed instances if they are part of the same service.
- Capture the output of
SELECT version();and the server’s package-manager version. - Record extension versions from the database catalog and note extensions that require a rebuilt binary for the target major.
- Document replication slots, physical or logical replicas, backup retention, and the last tested restore.
2. Map each instance to its support deadline
Compare every major version with the official support table. Calculate the remaining support window from the published final-release date, and prioritize PostgreSQL 14 because its fixes stop on November 12, 2026. Do not wait for an incident or a package repository to remove an old version before beginning the migration.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
3. Keep the source cluster current while you plan
Install the latest available minor release for the current major version before the major migration, subject to its release notes. Staying current reduces the number of known defects carried into testing and ensures that the source cluster has the latest security and data-integrity corrections.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →4. Select the migration method
Choose pg_upgrade when the cluster is large enough that a full logical export and import would take too long, and when your extensions and operating system support the tool. Choose dump/reload when you want a cleanly initialized target cluster, need an opportunity to remove obsolete objects, or have a database size and downtime budget that make logical migration practical.
A representative pg_upgrade invocation supplies the old and new binary directories and the old and new data directories. The exact options vary by installation, so use the target major version’s documentation and run the tool’s check mode before the cutover. A dump/reload plan should include a tested dump, transfer, restore, ownership and privilege recreation, extension installation, and sequence-value validation.
5. Test production-like behavior
Use an environment that matches production data volume, configuration, operating system, extensions, and representative traffic. A migration that succeeds on a small development database does not prove that production will meet its downtime or performance target.
- Run application integration and write/read tests, including transactions, prepared statements, time zones, and error handling.
- Compare query plans and latency for critical workloads; planner changes can make a previously stable index or join strategy behave differently.
- Exercise backups and perform a restore into the target major version.
- Validate physical and logical replication, failover automation, connection pools, monitoring exporters, and maintenance jobs.
- Install and test every extension before the migration window, including extension upgrades that must run inside the database.
6. Define cutover and rollback criteria
Write down the maintenance start and stop times, the person authorized to proceed, the validation queries, acceptable error and latency thresholds, and the exact point at which you will roll back. For pg_upgrade, preserve the old cluster until validation is complete. For dump/reload, keep the source database available or preserve a verified backup until the new cluster has passed application and restore checks.
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
If near-zero downtime is required, a replication-based migration may be possible, but it must be independently tested for your workload and PostgreSQL versions. Do not describe it as zero-risk: synchronization lag, sequence handling, extension state, and final write cutover still need explicit controls.
7. Validate after the switch
After cutover, verify application behavior before declaring success. Check connections, writes, background workers, scheduled jobs, dashboards, alerting, backups, replication lag, and failover status. Confirm that the server reports the intended major and current minor release, then monitor error rates and query performance through the first normal workload cycle.
How to choose a major-version target
The newest major version is not automatically the right target for every estate. Evaluate each candidate against the same decision axes:
| Decision axis | Questions to answer |
|---|---|
| Remaining support | How many years remain before the published final-release date, and when will the next migration be required? |
| Application and extension changes | Do drivers, extensions, authentication methods, SQL behavior, or configuration defaults require updates? |
| Migration effort | Can the chosen method fit the downtime budget, storage capacity, and operational skills? |
| Performance and features | Which measurable workload or operational problem is solved by the target version? |
| Platform availability | Are packages, container images, operating-system libraries, and monitoring integrations ready? |
| Replication and backup compatibility | Can replicas, backup agents, restore targets, and disaster-recovery procedures operate across the transition? |
| Next upgrade date | Will this target give the team a sustainable maintenance interval rather than another rushed migration? |
For minor releases, the decision is narrower: weigh the security urgency, the release-note impact, the amount of testing required, and the cost of the maintenance window. Because minor releases are the supported path for bug and security fixes, postponing them should be an explicit risk decision, not an accidental habit.
Free tools Windows power users keep installed
One-click scans. No signup required.
Downtime, staffing, and cost considerations
PostgreSQL itself is free software under the PostgreSQL Licence, including for commercial products. The cost of an upgrade is therefore operational: engineering time, test environments, additional storage, backup verification, migration tooling, application changes, and any production downtime. A major migration may also require temporary capacity for the old and new clusters at the same time.
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
Schedule the work when application owners, database administrators, infrastructure staff, and support personnel are all available. Include time for prechecks, backups, the migration, validation, and a rollback decision rather than reserving only the expected command runtime.
Common planning mistakes and their fixes
Treating a major upgrade like a patch
Installing new major-version binaries over an existing data directory is not the supported migration path. Use pg_upgrade or dump/reload and test the target cluster first.
Ignoring extensions and clients
The server may start successfully while an extension, driver, connection pool, or backup agent fails under application traffic. Inventory these dependencies and test them against the target version.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Waiting until EOL
PostgreSQL 14 has a fixed end date of November 12, 2026. Starting after that date leaves no supported source minor releases for new issues. Begin testing early enough to reserve a second maintenance window if the first attempt is rejected by validation.
Skipping intervening release notes
Even when a direct major-version jump is technically allowed, review the notes for every intervening major version. Configuration defaults, SQL behavior, authentication, extension requirements, and replication details can change between the source and target.
Assuming the calendar is immutable
Quarterly dates and the October 2026 PostgreSQL 19 target are planning guides. Emergency releases and changes to the final schedule can occur, so confirm the project’s release announcement and package availability before the production change.
Quick Recap
A compact decision checklist
- Is the cluster on a supported major version and its current minor release?
- What is the exact EOL date for the current major version?
- Are all extensions, drivers, operating-system packages, replicas, and backup tools compatible with the target?
- Has the chosen
pg_upgradeor dump/reload procedure passed a production-like rehearsal? - Are downtime, storage, staffing, validation thresholds, and rollback steps written down?
- After cutover, will monitoring, backups, replication, and application checks prove that the migration succeeded?
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors
