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
Short answer: a minor PostgreSQL update normally needs only new binaries and a restart, because minor releases keep the same storage format. A major-version upgrade is different: use pg_dump/pg_dumpall, pg_upgrade, or logical replication. Your downtime, rollback options, and preparation depend on that choice.
PostgreSQL major versions are supported for five years. In the current 2026 policy table, versions 18, 17, 16, 15, and 14 are supported; PostgreSQL 13 and older are outside community support. The sections below explain how to choose a method, estimate downtime without making false promises, and execute a controlled cutover.
First, identify whether this is a minor or major upgrade
Minor releases within the same major version
A minor release changes the last number, such as moving from 16.14 to 16.15. PostgreSQL documentation says minor releases never change the internal storage format and remain compatible with earlier and later minor releases of the same major version. In practice, you install the replacement server binaries, stop the instance, and restart it with the same data directory. A restart is still a service interruption, so schedule it and verify that connection pools reconnect correctly.
Minor updates can contain security fixes, bug fixes, and planner or replication corrections. Apply them through your operating-system packages or managed-service maintenance process, then check SELECT version(); and review the server log. Do not treat a minor update as permission to skip backup verification: a bad package, damaged disk, or configuration mistake can still make a restart fail.
#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.
Major releases
A major release changes the first number, for example 15 to 16 or 16 to 18. Major versions may change on-disk structures and introduce user-visible behavior changes. You cannot safely point a new major-version server at an old cluster directory. Use a logical dump and restore, pg_upgrade, or a replication-based migration instead.
Read the migration notes for every major version between your source and target, even when you intend to jump directly. A 15-to-18 project must review the 16, 17, and 18 migration sections. Test application drivers, SQL, extensions, authentication, and operational tooling before production cutover.
Which PostgreSQL versions are supported?
The PostgreSQL Global Development Group supports each major version for five years after its initial release. The following figures are from the project’s 2026 version policy table; minor numbers identify the current release listed there, not a promise that no later minor release will appear.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →| Major version | Current minor listed in 2026 | Final community release date | Status in the 2026 table |
|---|---|---|---|
| 18 | 18.6 | November 14, 2030 | Supported |
| 17 | 17.11 | November 8, 2029 | Supported |
| 16 | 16.15 | November 9, 2028 | Supported |
| 15 | 15.19 | November 11, 2027 | Supported |
| 14 | 14.24 | November 12, 2026 | Supported |
| 13 and older | Not listed as supported | Not applicable | Unsupported by the community policy |
If you are running PostgreSQL 13, the practical issue is not just access to new features. Community security and bug fixes no longer cover that major line, so plan a supported target and treat the project as a major upgrade.
Can you upgrade PostgreSQL without dump and restore?
Yes, but only by using another supported major-upgrade method. A filesystem-level backup or an old data directory cannot be attached directly to an incompatible major version. The three normal approaches have different operational costs.
| Method | How it moves data | Downtime shape | Strengths | Trade-offs |
|---|---|---|---|---|
| Dump and restore | Exports logical objects and rows with pg_dump or pg_dumpall, then recreates them on the target. |
The source normally pauses writes for the dump/cutover plan, and the target is unavailable while restore runs. Total time follows data volume, object count, indexes, and hardware. | Portable, straightforward, and independent of the source cluster’s physical layout. | Usually the longest outage; restore ordering, extensions, roles, and ownership need careful checking. |
pg_upgrade |
Converts a cluster in place using the old and new server installations. | Most work is prepared before the stop; the final outage is the time needed to run the upgrade, start the new cluster, and validate it. | Usually much faster than a full logical export and restore. | Requires compatible binaries, extensions, tablespaces, authentication, and standby planning. Disk mode affects rollback. |
| Logical replication | Synchronizes a new cluster while the old primary continues serving traffic, then redirects clients. | The official guide describes a switchover of only several seconds; this is a method characteristic, not a guaranteed production result. | Allows parallel build and testing and can minimize the write pause. | More setup, replication monitoring, object-by-object compatibility work, and a failback plan for writes after promotion. |
Choose using six questions: how long a planned write pause your application can tolerate, how much free storage is available, whether every extension exists for the target, how much operational complexity your team can absorb, how simple rollback must be, and whether replication lag can be monitored reliably.
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
How much downtime should you expect?
Why there is no universal number
Neither PostgreSQL documentation nor the project policy publishes a universal upgrade-duration benchmark. Time depends on database size, number and size of indexes, tablespace layout, extension behavior, disk and CPU speed, authentication configuration, replication lag, and the chosen method. Measure your own production-like dataset rather than quoting a vendor-style estimate.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteDump and restore timing
Benchmark both commands separately: export a representative backup and restore it into a clean target. Include creation of indexes, constraints, ownership, grants, extensions, and post-restore analysis in the stopwatch. If the restore requires a longer write freeze than the business can accept, switch to pg_upgrade or replication instead of hoping to optimize an outage you have not measured.
pg_upgrade timing
Run the preflight checks and a rehearsal on a copy of the cluster. Measure the stop, upgrade, new-server start, application checks, and any required extension work. Large clusters often spend most elapsed time in validation and post-upgrade maintenance rather than in the command that changes the cluster, so include those tasks in the change window.
Logical-replication timing
Replication moves most data before cutover. Your measured outage is the time to stop or fence writes, wait for the target to catch up, promote or redirect traffic, refresh connection pools, and run smoke tests. “Several seconds” applies to the documented switchover behavior, not to a complete migration project; lag, blocked sessions, DNS or service-discovery caching, and application retries can make the real interruption longer.
Preparing a major-version upgrade
1. Inventory the source and target
- Record exact source and target major and minor versions, operating-system packages, server binaries, and compile-time options.
- List every installed extension and confirm a target-compatible build is available.
- Document databases, roles, grants, authentication rules, collations, tablespaces, foreign-data wrappers, replication slots, standbys, client drivers, connection-pool settings, and backup jobs.
- Identify application queries that depend on planner behavior, implicit casts, time-zone abbreviations, or deprecated settings.
2. Read every intervening migration note
Migration notes describe compatibility changes that can require code or configuration changes. PostgreSQL 18 notes, for example, call out time-zone abbreviation handling and checksum defaults. Do not assume that a direct version jump avoids changes introduced in releases you skipped.
3. Rehearse with production-like data
Restore a verified backup into an isolated target, or clone the source for a pg_upgrade rehearsal. Run representative application tests, migrations, reporting jobs, background workers, and failover procedures. Compare row counts, schema objects, permissions, extension versions, query errors, and latency-sensitive queries.
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.
4. Define acceptance and rollback criteria
Write pass/fail checks before the maintenance window. Include application health, connection counts, error rates, replication state, critical query results, scheduled jobs, and backup completion. Set a time-bounded rollback decision: continuing to troubleshoot indefinitely can create more risk than returning traffic to the old system while the incident is understood.
Using pg_upgrade safely
Run the check before changing data
Use the new server’s pg_upgrade utility and run pg_upgrade --check against the source and target installations. The check validates many prerequisites without performing the migration. Treat every reported issue as a release blocker until it is fixed and the check passes again.
Confirm that the old and new binaries are compatible, required extensions are installed for both versions, tablespaces are accessible, authentication files and service accounts are correct, and standby procedures are documented. A clean check is not a substitute for application testing; it does not prove that every query or extension behaves as expected.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Choose link mode or clone mode deliberately
Link mode is fast and uses less additional disk space because the new cluster links to existing files. Its rollback limitation is decisive: once the new cluster starts, the old cluster cannot be accessed. Preserve a separate verified backup before proceeding.
Clone mode can provide similar speed and space benefits while preserving the old cluster on supported operating systems and filesystems. Confirm that your platform supports cloning and that the resulting copy is protected from accidental writes. Whichever mode you choose, document exactly which directory is authoritative after cutover.
Handle standbys and slots
Inventory physical and logical standbys, replication slots, monitoring agents, and backup integrations. Recreate or redirect them using procedures tested against the target version. PostgreSQL 17.0 and later support migration of logical-replication slots through pg_upgrade; older source versions may have slots ignored and require manual handling.
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.
Using logical replication for a low-interruption cutover
Build and synchronize the target
Install the target major version, create the required roles and schema, and configure logical publication and subscription according to the target’s requirements. Keep the old primary serving traffic while the initial copy and ongoing changes are applied. Monitor apply errors, lag, conflicts, sequences, large objects, and objects that logical replication does not automatically reproduce.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteLogical-replication migration of a cluster is supported only when every member of the old cluster is PostgreSQL 17.0 or later. If any member is older, use another method or upgrade the members first; do not assume that a partially upgraded topology is covered.
Freeze writes and switch traffic
- Announce the change and stop scheduled jobs or workers that could create writes during the handoff.
- Pause application writes or place the service in a maintenance mode while reads are assessed.
- Wait until the target has applied all required changes and verify replication state.
- Redirect the application, service discovery, or connection pool to the target.
- Run smoke tests for authentication, critical reads and writes, background jobs, and monitoring.
- Keep the old cluster intact but fenced from accidental writes while the acceptance window runs.
Plan for non-transactional edge cases
The official guidance warns that multi-node logical-replication procedures are not fully transactional. Take verified backups and decide how to reconcile writes made after promotion. A failback is not simply a DNS reversal if the new primary accepted data; you must either replicate changes back, restore from a defined point, or reconcile them according to an agreed business procedure.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Rollback: what is actually possible?
Before the new cluster starts
For a dump/restore migration, the old cluster remains the source until you deliberately redirect traffic. For pg_upgrade, a stopped old cluster can generally be retained while checks run, provided your chosen mode and filesystem layout allow it. Keep the verified backup independent of both clusters.
After a pg_upgrade cutover
Link mode removes access to the old cluster once the new cluster starts, so it is not an instant back button. Clone mode can preserve an old copy where supported, but you still need to prevent split-brain writes and define which copy is authoritative. Rollback means stopping the target, restoring the old service or copy, reversing client configuration, and assessing any writes accepted after cutover.
After logical-replication promotion
Reverse traffic only after deciding what happens to data written on the promoted target. Preserve logs and backups, fence the failed target, and use a tested reconciliation or re-seeding process. Without that plan, a quick DNS change can silently lose or duplicate transactions.
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.
Cutover checklist and post-upgrade work
Immediately before maintenance
- Verify a recent backup can be restored and that monitoring, paging, and console access work.
- Confirm the change window, owners, communication channel, rollback deadline, and traffic-control mechanism.
- Disable automated jobs that could conflict with the migration.
- Record baseline health: connection counts, replication lag, error rates, storage, and critical query results.
During cutover
- Follow the rehearsed runbook rather than improvising commands.
- Capture command output and timestamps.
- Check server logs for extension, authentication, collation, checksum, and recovery errors.
- Validate schema objects, roles, grants, sequences, extensions, tablespaces, and replication before opening all traffic.
After acceptance
Run the target release’s required extension updates and post-upgrade maintenance. Refresh statistics when appropriate, verify backup jobs and standbys, remove temporary replication objects only after the retention decision, and monitor query plans and application errors for several business cycles. Retain the old cluster or clone for the agreed rollback window, then decommission it only after the final backup and data-retention checks pass.
Common failure modes and responses
The new server refuses to start
Check the log first for an incompatible data directory, missing extension library, wrong ownership, port conflict, invalid authentication rule, or inaccessible tablespace. Do not repeatedly restart against a directory whose provenance is unclear; stop, preserve logs, and return to the rehearsed recovery point.
An extension is missing or fails to load
Install the target-version extension package before cutover and test CREATE EXTENSION or the required upgrade path in the rehearsal environment. An extension that exists on the old host but not in the new installation is a migration blocker, not a cosmetic warning.
Recommended Free Tools
Logical replication is behind
Keep the old primary serving traffic, inspect apply errors and conflicts, and measure whether lag is decreasing. Do not switch merely because the target is reachable. If the lag cannot be eliminated within the window, postpone or use the documented rollback path.
Application behavior changes after success
Compare failed queries, query plans, time-zone results, casts, permissions, and driver logs with the baseline. Review every intervening major release’s migration notes, then fix the application or configuration before declaring the upgrade complete.
Decision guide
- Choose a minor update when the major number stays the same; replace binaries, restart, and validate.
- Choose dump and restore when portability and procedural simplicity matter more than outage length and the measured restore fits the window.
- Choose
pg_upgradewhen you need a faster major migration and can satisfy binary, extension, filesystem, and rollback requirements. - Choose logical replication when a parallel build and a very short planned write pause justify additional setup, monitoring, and data-reconciliation work.
There is no safe shortcut that consists of attaching an old data directory to a new major server. Backups, rehearsals, migration-note review, explicit acceptance tests, and a rollback decision are the controls that make a major-version upgrade predictable.
Quick Recap
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
