-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Update PostgreSQL to 11 #195
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Last time I run the tests from netbox with Postgres 12 I had some failures, that weren't there with 10 or 11. If they are gone now, I think the upgrade is OK. If not we should only go to version 11.
I did not do extended testing, so I trust in your judgment. 11 it is for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good idea to go to 11.x so we always have the current minor version 👍
Hi!
is there a prefered way to upgrade the database? Thank you! |
Thank you for making me aware of this. Since I only use the Docker image for development, I can not provide a tried-and-tested answer to that question of yours. There seem to be several proposals flowing around:
Note that there is no requirement to update to PostgreSQL 11, you can stick to version 10 just fine. version: '3.4'
services:
postgres:
image: postgres:10-alpine I have added a note to the preliminary changelog of the 0.20.0 release about this. |
No description provided.