In testing our upgrade from 3.18.8 -> 3.24.x I also wanted to upgrade postgres from 8.1 to 8.3.
Here are the procedures that I used for our Debian system:
#apt-get install postgresql-8.3
#pg_dropcluster --stop 8.3 main
#pg_upgradecluster 8.1 main
#pg_dropcluster --stop 8.1 main
#apt-get remove postgresql-8.1
This seemed to work perfectly, it upgraded the database and the front end site and _admin seem to be fine.
I just wanted to make sure there are no other issues that Squiz has experienced with 8.3 or upgrading, or if there are other things I should test to make sure it will go ok.
In testing our upgrade from 3.18.8 -> 3.24.x I also wanted to upgrade postgres from 8.1 to 8.3.
Here are the procedures that I used for our Debian system:
#apt-get install postgresql-8.3
#pg_dropcluster --stop 8.3 main
#pg_upgradecluster 8.1 main
#pg_dropcluster --stop 8.1 main
#apt-get remove postgresql-8.1
This seemed to work perfectly, it upgraded the database and the front end site and _admin seem to be fine.
I just wanted to make sure there are no other issues that Squiz has experienced with 8.3 or upgrading, or if there are other things I should test to make sure it will go ok.
[/quote]
No, you shouldn't have any problems running 8.3. We have 8.3 unit tests running daily and also use 8.3 in our dev environment.
You'll have to check your postgres settings (shared_buffers, effective_cache_size, checkpoint_*, and bgwriter_* settings are the most important for matrix I think). The other notable thing is that in the postgresql.conf, 8.3 added support for easy memory notations so instead of having to calculate shared_buffers and other settings as number of blocks, you can just give it memory (eg '512Mb' instead of 16384 or whatever it'd work out to be).