It looks like Fly MPG is Postgres 16. Are there plans / timelines to support 17 (or dare I hope, 18)?
Hey Jeffrey, currently no firm plans to ship either version—though PG17 wouldn’t be super complicated to get out.
Curious what features you need from the newer versions, if you’d like to share.
I would expect a reasonable delay but not no firm plans. A 3-month delay would be preferred as that follows the minor release cadence, but 6-months seems reasonable given Fly’s size. At the very least downgrading just to switch to MPG is a tough pill to swallow. I suspect I’m not the only fly customer in that boat.
The lack of JSON TABLE support which was introduced in PG17 would be a deal breaker for us. So is the 1TB disk limit for our Prod and QA systems, but would be fine for our short lived Feature testing.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.