- Services
- Projects
- Resources
- Upcoming Training
- Webinars
- Manager Guides
- Whitepapers
- High-Performance PostgreSQL: A Practical Guide to Optimization
- Transitioning from Oracle to Postgres: A Comprehensive Comparison
- Benchmark Study on Replication Lag in PostgreSQL Using Single-Region and Multi-Region Architectures
- Transparent Data Encryption and High Availability
- Data Ingestion Benchmark Comparison Between PostgreSQL and MongoDB
- Case Studies
- Supabase SaaS Customer – PostgreSQL Performance Tuning
- Fraîcheur de Paris – Database Performance Optimization
- Last Mile Delivery App – Massive Postgres Performance Improvement
- SaaS Video Platform – Expert Postgres Troubleshooting
- Middle Eastern Govt – 99.99% Availability Solution
- Fortune 500 – Data Engineering and BI Setup
- Whop – Database Infrastructure Migration
- FinTech – High Availability Cluster
- Ventrata – Migration and Performance Tuning
- Industry
- Postgres Talks
- Blogs
- About Us
- Contact Us
PostgreSQL 14: end of life Nov 12, 2026
PostgreSQL 15: end of life Nov 11, 2027
Upgrade PostgreSQL once. Stay supported until 2030.
Our Postgres FDEs upgrade your production database to PostgreSQL 18 with a blue-green upgrade and minimal downtime. Your application keeps running; the switchover is a write pause of seconds.
Which version are you on?
SELECT version();14 or older: you are running without security fixes today.
15: you have one year to plan, test and cut over.
16: you have two years.
15: you have one year to plan, test and cut over.
16: you have two years.
Every major version gets five years of community support.
Upgrading to PostgreSQL 18 buys you four years of community support, until November 14, 2030.
PostgreSQL 14End of life Nov 12, 2026
End of life Nov 12, 2026
PostgreSQL 15End of life Nov 11, 2027
End of life Nov 11, 2027
PostgreSQL 16End of life Nov 9, 2028
End of life Nov 9, 2028
PostgreSQL 17Ends Nov 8, 2029
Ends Nov 8, 2029
PostgreSQL 18Recommended · Nov 14, 2030
Recommended · Nov 14, 2030
2021
2023
2025
Today
2029
2031
How we upgrade without taking you offline
Your current cluster (blue) keeps serving production while the new version (green) is built and kept in sync beside it. You switch only when green has been tested with your application.
STEP 1
Blue: current cluster
Your old Postgres keeps serving production, untouched.
STEP 2
Logical replication
Every change replicates to the green cluster on PostgreSQL 18.
STEP 3
Green: test and rehearse
Your application runs against the new version. We rehearse the switchover until we get it perfect.
STEP 4
Cutover
Traffic moves to green. Write pause: seconds.
STEP 5
Hypercare
One week of close monitoring after cutover, so any issue is caught and fixed before it affects your business.
Safety net: for 5 days after cutover, replication runs in reverse, from green back to blue, so you can switch back with every write intact.
Downtime by method
The method decides how long your application waits. We use a blue-green upgrade wherever the cluster qualifies.
Dump and restoreHours, grows with size
pg_upgrade --linkMinutes
Blue-green with logical replication (our default)Seconds
Bars are illustrative, not to scale.
Results
Under 10 minutes
100 GB production database upgraded with pg_upgrade, where a blue-green upgrade was not an option.
Close to zero downtime
Production clusters for a banking software provider, upgraded from PostgreSQL 13 to 17 with a cutover of a few seconds.
What you get
- Postgres FDEs working closely with your team to ensure smooth upgrades
- Readiness review: extensions, schema, replication, connected pipelines
- Green cluster on PostgreSQL 18, built to production standards
- Blue-green setup: logical replication, sync monitoring and application testing
- Rehearsed switchover in a window you choose
- Post-upgrade checks and a written report
- About two weeks from start to switchover
You provide: access to the database, a test environment for your application, and a contact who can approve the cutover window.
Starting from
$9,990
per cluster
Very large databases, unsupported extensions or tables without primary keys are scoped on the review call.
Book a 30-minute upgrade reviewQuestions we hear
We run on a managed service. Can you still help?
Yes, on every managed service, including Amazon RDS, Aurora, Cloud SQL, Azure and Supabase. We use the upgrade path each platform supports.
What if we stay on 14?
It keeps running, but no new security or bug fixes will ship for it. Each new vulnerability stays open on your servers.
Why not upgrade to 15, 16 or 17?
Same effort, fewer years. PostgreSQL 18 is supported until November 14, 2030.
Why PostgreSQL 18 and not 19?
For production databases, we recommend the release one behind the newest. PostgreSQL 18 has had a year of minor releases and is running in production widely, and it stays supported until November 14, 2030. A new major version earns the same standing after its first round of minor releases. When a customer has a specific need for the newest version, we plan for it on the review call.
Our database is very large.
Size changes how long replication takes to catch up, not the write pause at cutover.
AWS offers Blue/Green Deployments. Why bring in Stormatics?
AWS Blue/Green Deployments use the same logical replication on RDS and Aurora. They do not support major upgrades from some older minor versions and have no built-in rollback after switchover. We run the review, the upgrade and the switchover on any platform, and replicate from green back to blue for 5 days after cutover, so a rollback keeps every write.
What can stop a near-zero cutover?
Large objects, tables without primary keys and schema changes during the upgrade. The review call finds these first.
How long does it take?
About two weeks from start to switchover, including planning and rehearsals, followed by one week of hypercare.
Book your upgrade slot
30 minutes with a Postgres FDE. You leave with a target version, a method and a date.

