-
Notifications
You must be signed in to change notification settings - Fork 485
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
support PostgreSQL 14 #8295
Milestone
Comments
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
Dec 8, 2021
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
Feb 4, 2022
Speaking of bumping Flyway, I noticed this WARN on a 5.9 test instance just now:
|
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
May 12, 2022
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
May 12, 2022
donsizemore
pushed a commit
to uncch-rdmc/dataverse
that referenced
this issue
May 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The integration test suite results look normal on PostgreSQL 14:
however, in server.log, Flyway 5.2.4 complains that it hasn't with PostgreSQL 14.
I bumped Flyway to its current version, 8.2.0, and the PostgreSQL JDBC driver to 42.3.1 for all the bugfixes. Integration test results appear similar when the above configuration is run on PostgreSQL 13, which IQSS currently recommends:
Pull request forthcoming.
The text was updated successfully, but these errors were encountered: