gotchasqlMinor
A confusing thing said in the PostgreSQL manual:
Viewed 0 times
postgresqltheconfusingmanualsaidthing
Problem
For some releases, manual changes may be required to complete the upgrade, so always read the release notes before upgrading.
Source: https://www.postgresql.org/support/versioning/
It's talking about some minor releases in the quoted sentence.
-
Doesn't this mean that it's impossible to automate updating of PostgreSQL, even for minor versions?
-
What kind of "manual steps" are required, and how often is that the case?
This is exactly the kind of thing which makes me scared of and unwilling to update software, even crucial core software like PostgreSQL. I'm 100% sure that I'm not the only one who just mentally blocks out the need to update software when we read remarks like this. The thought of manually having to keep track of every damn changelog is literally Hell to most of us.
Source: https://www.postgresql.org/support/versioning/
It's talking about some minor releases in the quoted sentence.
-
Doesn't this mean that it's impossible to automate updating of PostgreSQL, even for minor versions?
-
What kind of "manual steps" are required, and how often is that the case?
This is exactly the kind of thing which makes me scared of and unwilling to update software, even crucial core software like PostgreSQL. I'm 100% sure that I'm not the only one who just mentally blocks out the need to update software when we read remarks like this. The thought of manually having to keep track of every damn changelog is literally Hell to most of us.
Solution
I think the technical term for this sort of thing is "Covering your Behind".
All it's saying is that upgrades will work in the vast majority of cases but acknowledges that there's an outside chance that somebody, somewhere has got some convoluted set-up that means an extra step or two might be needed. If the PostgreSQL team think that's a possibility for any given upgrade, then they'll tell us so and we can work out whether or not the problem case(s) apply to us and we can do the extra work, if necessary.
I would never contemplate completely automating database upgrades.
Databases are complex Beasties and can be "upset" by any number of things. Having them "upset" in the middle of an upgrade is a really Bad Place to be.
Of course, you want to script up as much as you can, but you have to accept that you cannot cater for every possible eventuality. You should always have somebody around during the upgrade, just in case.
All it's saying is that upgrades will work in the vast majority of cases but acknowledges that there's an outside chance that somebody, somewhere has got some convoluted set-up that means an extra step or two might be needed. If the PostgreSQL team think that's a possibility for any given upgrade, then they'll tell us so and we can work out whether or not the problem case(s) apply to us and we can do the extra work, if necessary.
I would never contemplate completely automating database upgrades.
Databases are complex Beasties and can be "upset" by any number of things. Having them "upset" in the middle of an upgrade is a really Bad Place to be.
Of course, you want to script up as much as you can, but you have to accept that you cannot cater for every possible eventuality. You should always have somebody around during the upgrade, just in case.
Context
StackExchange Database Administrators Q#265247, answer score: 3
Revisions (0)
No revisions yet.