Commit to keeping Timescale updated
The Timescale extension is a year behind on releases. Last time we tried it, it was also far behind, and buggy.
This lack of updates is reason enough for us not to try and use it.
Please commit to keeping Timescale, end extensions in general, up-to-date.
Not having to manage updates outselves is, after all, a large part of the value a managed solution provides.
This is such a bummer. Azure is limited to Postgres 11 with Timescaledb 1.3.2, ages behind the latest version. Digital Ocean supports Postgres 12 with Timescaledb 1.7.1. The new "Flexible Preview" supports postgres 12 but doesn't support timescaledb.
What is Azure waiting for to upgrade?
Is there any possible update on this topic? Without being able to leverage Timescale's compression, we will soon be forced to decide if running Postgresql in Azure is worth the cost, vs moving it back on-prem.
Azure PostgreSQL should also support the PSL and Community license schemas, as some very useful timescaleDB functions are now blocked/not usable due Azure PostgreSQL being on the apache only license.
Update to support minimum of 1.5 please! I see little justification in the SQL service offerings when a VM with no limits offers better performance at a lower cost.
Jouke Aalvanger | Verbruggen commented
This is also very important for us. We choose TimescaleDB for the functions they provide, but they are not available with the current version...
Please update the extension.
Brent Smith commented
This is extremely important. If MS is not committed to keeping extensions up to date then the supported extensions are not production ready at all. I have been evaluating TimescaleDB but it's problematic if the versions are far behind.
What about partnering with the TimescaleDB team to keep up the extension?
In general Azure PostgreSQL is pretty fantastic, but this is an important hole in the offering.
This is very important.
Not to minimize the work, but can't we automate the inclusion of the latest versions of extensions and allow the customer to opt-in while acknowledging this version is untested (until, of course, it is tested)?
This functionality would make Az pg much, much more usable.
Anderson, Colin D commented
Also really keen to have at least 1.7.0 on Azure, but really the Azure team needs to commit to keeping extensions updated - at present only 1.3.2 is available, which is more than a year old.
Alternatively, we need a mechanism so users can install their own extensions.
I want to use Azure's Managed Postgres, but you make it so difficult to choose when the extensions are so woefully out of date!
we need an update to 1.5 minimum to offer better solution
We need to go to 1.5 minimum
Martin Helmer commented
Currently we are using the timescale SaaS offering due to this limitation. If Azure provided better support for this extension the managed postgres instances would become an option for us.