Hi :)
I do have a test enviroment and I will test eveything there first but I had cases where eveything worked on test but on production I had difficultes. It's rare but can happen.
Problems with upgrading PostgreSQL isn't like upgrading a package which effects few functions.
Since the documntation says just replace the executables I'm lost...
I notced that 9.3.5 and 9.3.9 requires sepcific test. Further more it says secificly not to perform the tests for 9.3.9 with versions piror to 9.3.5 as it might not work : "The lingering effects of a previously-fixed bug in pg_upgrade could also cause such a failure, in installations that had used pg_upgrade versions between 9.3.0 and 9.3.4." So this means I have to upgrade to 9.3.5 and only then to 9.3.16
How do I perform upgrade in steps to specific versions?
I'm runing 9.3.3 in production server and in test server.
Operating system is Ubuntu server 12
I'm still not sure that I can upgrade directly from 9.3.3 to 9.3.16 - The documntation always tells to "if you are upgrading from version earlier than 9.3.X check 9.3.X-1". It assums that everyone upgrading once the version was released which is not always the case. And as mentioned earlier 9.3.5 and 9.3.9 can create problems as they require specific checks.
I'd appriciate any insight.
×? ×?פר׳ 26, 2017 13:26, Sameer Kumar ×?ת×?:
On Wed, Apr 26, 2017 at 4:41 PM Ron Ben <ronb910@xxxxxxxxxxx> wrote:I'm runing PostgreSQL 9.3.3 and I want to upgrade it to the latest 9.3 versionThe documontation does not specify what needs to be done other than "just install the executables".This is wierd as for example 9.3.5 release notes request to run a specifc query to check for pg_multixact files left.I saw this question:I'm not sure how this will handle the 9.3.5 check issue.What is the version of PostgreSQL that you are running?Though there are some general guidelines/procedure (which is as simple as stop the server, upgrade binaries and start, there will also be some peculiar releases which has a bug-fix. While the bug-fix covers you in future, there might have been incidents where you are already bitten by bug being fixed (worse if you have not yet identified it). To cover such cases, you would need to follow some custom procedure. Again, mostly the custom steps are not for patch application but more of a mitigation against risks of bug or in some cases bug-fix.Are you running with a standby or just stand-alone setup?Is it really just runing one command?What if there are errors and problems? how do i revert back?Sadly there is not enough information regarding minor verion updates...I'm also runing ubuntu server 12 which will be updated as well later this quarter.Do you have a test environment? If I were you I would have a non-prod that mimics my production setup exactly and I would apply the patch there first.--Sameer Kumar | Senior Solution Architect
ASHNIK PTE. LTD.
101 Cecil Street, #11-11 Tong Eng Building, Singapore 069533
T: +65 6438 3504 | www.ashnik.com
Skype: sameer.ashnik | M: +65 8110 0350
