Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostgreSQL 11 support #2178

Closed
axelfontaine opened this issue Oct 18, 2018 · 11 comments
Closed

PostgreSQL 11 support #2178

axelfontaine opened this issue Oct 18, 2018 · 11 comments

Comments

@axelfontaine
Copy link
Contributor

@axelfontaine axelfontaine commented Oct 18, 2018

No description provided.

@whaleyr
Copy link

@whaleyr whaleyr commented Oct 24, 2018

I just tried 11 today. I was able to run the migrate tasks just fine. However, I did a clean and it borked when trying to query pg_proc for column pgisagg which has been removed between 10 and 11.

Keep up the good work, I'll be glad to see 6.0.0 when it's ready.

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Nov 29, 2018

This has now been integrated via @tinybarks 's awesome pull request. Thanks!

@markusheiden
Copy link

@markusheiden markusheiden commented Jan 23, 2019

Since the 6.0.0 seems to be far away: Are there any plans for a backport?

@ragged
Copy link

@ragged ragged commented Jan 23, 2019

We also have a big need for the 6.0.0 release, as a lot of upgrades are currently postponing, due to the lack of flyway support. How likely is 6.0.0 is on time?

@ssonnenberg
Copy link

@ssonnenberg ssonnenberg commented Feb 8, 2019

Yes, we are waiting. PostgreSQL 11 is available since November, so if anything is blocking
this small fix than please give us some details.

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 12, 2019

We have now pushed the out as part of Flyway 6.0.0-beta. See https://flywaydb.org/blog/flyway-6.0.0-beta

As part of this release, we are also making some changes to our support timeline for new database versions. Previously we added support for a new database version once it reached GA. We have now changed this and started adding support for a new database version once it reaches beta. The first database versions to benefit from this are SQL Server 2019 CTP and MariaDB 10.4 beta. Support for both of these is already included as part of 6.0.0-beta.

Going forward we will add support for PostgreSQL 12 as soon as a first beta is released, which will be many months before GA, so that a wait like the one for PostgreSQL 11 won't happen again.

@ssonnenberg
Copy link

@ssonnenberg ssonnenberg commented Feb 12, 2019

Great news. Will you provide maven coordinates to enable wider testing?

@axelfontaine
Copy link
Contributor Author

@axelfontaine axelfontaine commented Feb 12, 2019

@dahu33
Copy link

@dahu33 dahu33 commented Aug 7, 2019

PostgreSQL 11 was released 10months ago, PostgreSQL 12 is in beta 2 and there is still no stable version of flyway supporting them. I don't understand the strategy of blocking people and companies by not adding compatibility in Flyway v5, especially since the required code change is trivial...

@douglasrlee
Copy link

@douglasrlee douglasrlee commented Aug 12, 2019

So, is the plan here just to wait for pg 12 and flyway 6?

@SebHeuze
Copy link

@SebHeuze SebHeuze commented Aug 12, 2019

Hi, is 14/08/19 still the release date planned for 6.0.0 release ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants