Thread: Upgrade
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I've got a somewhat 'hairy' problem in my hands... One of my servers is still Fedora Core (cough) (cough) 6 :] It's running Postgresql 8.2.4 I want it to serve as a last resort, end of the spectrum, backup/slave for another server running Postgresql 8.2.9 via Slony-I. The other server is running Postgresql 8.2.9 over Fedora Core 8. First challenge: I need to upgrade to postgresql 8.3 if I'm to use Slony-I 2.0.2 on both servers. At a glance I feel that upgrading the FC6 server is the hairiest of tasks to be accomplished. Regarding the FC8 (a.k.a. master wannabe): would an upgrade from 8.2.9 to 8.3 require a dump/reload ? The DB size on this server is not that big (~6GB), although a single table has >8.3M rows, meaning that if a dump/reload is involved I'm looking at several hours of out of service (sweat)... Insight on how to tackle the upgrade for these two servers (especially the FC6 one) would be much appreciated! ;-) Thanks in advance. BR. - -- Pedro Doria Meunier GSM: +351 96 17 20 188 Skype: pdoriam -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKQ2eq2FH5GXCfxAsRAvqkAJwOrlUSI37IdbiaFmnWfkBo4hakkwCeMugm NbYacw6nox6xubq3llNR0xk= =f862 -----END PGP SIGNATURE-----
In response to Pedro Doria Meunier <pdoria@netmadeira.com>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi all, > > I've got a somewhat 'hairy' problem in my hands... > > One of my servers is still Fedora Core (cough) (cough) 6 :] > It's running Postgresql 8.2.4 > > I want it to serve as a last resort, end of the spectrum, backup/slave > for another server running Postgresql 8.2.9 via Slony-I. > > The other server is running Postgresql 8.2.9 over Fedora Core 8. > > First challenge: I need to upgrade to postgresql 8.3 if I'm to use > Slony-I 2.0.2 on both servers. > > At a glance I feel that upgrading the FC6 server is the hairiest of > tasks to be accomplished. > Regarding the FC8 (a.k.a. master wannabe): would an upgrade from 8.2.9 > to 8.3 require a dump/reload ? > The DB size on this server is not that big (~6GB), although a single > table has >8.3M rows, meaning that if a dump/reload is involved I'm > looking at several hours of out of service (sweat)... > > Insight on how to tackle the upgrade for these two servers (especially > the FC6 one) would be much appreciated! ;-) Why don't you set up Slony to replicate data between the two, then you can take the slave offline to upgrade it to PG 8.3, then switch the slave to be the master, then upgrade the other. We just did that with 4 DB servers (all replicas of the same DB) a few weeks ago and it went fine. It was a 5G database and half of the servers were replicating across the country. We're looking at the upgrade to Slony 2 as a separate step. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/
On Thu, Jun 25, 2009 at 10:04 PM, Pedro Doria Meunier <pdoria@netmadeira.com> wrote:
You would need to do a dump restore when upgrading from 8.2.9 to 8.3.
Guy Flaherty
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi all,
I've got a somewhat 'hairy' problem in my hands...
One of my servers is still Fedora Core (cough) (cough) 6 :]
It's running Postgresql 8.2.4
I want it to serve as a last resort, end of the spectrum, backup/slave
for another server running Postgresql 8.2.9 via Slony-I.
The other server is running Postgresql 8.2.9 over Fedora Core 8.
First challenge: I need to upgrade to postgresql 8.3 if I'm to use
Slony-I 2.0.2 on both servers.
At a glance I feel that upgrading the FC6 server is the hairiest of
tasks to be accomplished.
Regarding the FC8 (a.k.a. master wannabe): would an upgrade from 8.2.9
to 8.3 require a dump/reload ?
The DB size on this server is not that big (~6GB), although a single
table has >8.3M rows, meaning that if a dump/reload is involved I'm
looking at several hours of out of service (sweat)...
Insight on how to tackle the upgrade for these two servers (especially
the FC6 one) would be much appreciated! ;-)
You would need to do a dump restore when upgrading from 8.2.9 to 8.3.
Guy Flaherty
On Thu, Jun 25, 2009 at 1:28 PM, Guy Flaherty<naoshika@gmail.com> wrote: > One of my servers is still Fedora Core (cough) (cough) 6 :] > It's running Postgresql 8.2.4 > > I want it to serve as a last resort, end of the spectrum, backup/slave > for another server running Postgresql 8.2.9 via Slony-I. Before doing anything else you should upgrade both of these to 8.2.13. There's no point in running software with known bugs and security holes when there are updates available. -- greg http://mit.edu/~gsstark/resume.pdf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 First of all, thank you all who have replied so far :) The FC8 server has been upgraded to 8.2.13 with minor "glitches" :) I'm one step shy of upgrading it to 8.3 :P Btw: I'm using the http://yum.pgsqlrpms.org/ repository as the source for the upgrade. After dumping the DB and stopping the server, should I remove all PGSQL rpms via yum and then install the pgdg-fedora-8.3-6.noarch <http://yum.pgsqlrpms.org/reporpms/8.3/pgdg-fedora-8.3-6.noarch.rpm> and continue on to the upgrade? As far as the older FC6 server is concerned to my great frustration this arch is EOL and there are no upgrade packages available... :-( Perhaps someone is able to conjure up some sort of solution for this? TY, Pedro Doria Meunier GSM: +351 96 17 20 188 Skype: pdoriam Greg Stark wrote: > On Thu, Jun 25, 2009 at 1:28 PM, Guy Flaherty<naoshika@gmail.com> > wrote: >> One of my servers is still Fedora Core (cough) (cough) 6 :] It's >> running Postgresql 8.2.4 >> >> I want it to serve as a last resort, end of the spectrum, >> backup/slave for another server running Postgresql 8.2.9 via >> Slony-I. > > Before doing anything else you should upgrade both of these to > 8.2.13. There's no point in running software with known bugs and > security holes when there are updates available. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFKQ5fa2FH5GXCfxAsRAhllAJ4rLBABOm0eX8NdYGhNgLn8rybvJQCgoV/Q W1y8JfZlkmrGs72YOPCawZI= =2gPK -----END PGP SIGNATURE-----