Thread: 7.2 - 7.4.2 production server migration issue
Hi everyone at the list,
Some months ago i asked you some questions about 7.2 - 7.4.3 migration. Then i switched to the performance list to complain about postgres 7.2 poor performance and discussed about different ways to improbe performances.
Two days ago we started our first production server 7.4.2 migration at our biggest customer, a quite big postgres 7.2 database with millions of rows in a quite complex scheme.
I must say that the result is even better than what we expected. The average load of the standalone database server used to be around 1.5 - 2.0 with 7.2
The 7.4.2 server load average is now around 0.5 !!
The new database is answering very quickly at each request, and web pages displays quicker as never before.
I'm here to say thank you for your great work guys. Nice job!
I'm now waiting for 7.5 :)
++
Christophe Musielak
Some months ago i asked you some questions about 7.2 - 7.4.3 migration. Then i switched to the performance list to complain about postgres 7.2 poor performance and discussed about different ways to improbe performances.
Two days ago we started our first production server 7.4.2 migration at our biggest customer, a quite big postgres 7.2 database with millions of rows in a quite complex scheme.
I must say that the result is even better than what we expected. The average load of the standalone database server used to be around 1.5 - 2.0 with 7.2
The 7.4.2 server load average is now around 0.5 !!
The new database is answering very quickly at each request, and web pages displays quicker as never before.
I'm here to say thank you for your great work guys. Nice job!
I'm now waiting for 7.5 :)
++
Christophe Musielak
On Fri, Jul 30, 2004 at 14:32:02 +0200, Christophe Musielak <cmusielak@akio-software.com> wrote: > > Two days ago we started our first production server 7.4.2 migration at > our biggest customer, a quite big postgres 7.2 database with millions of > rows in a quite complex scheme. 7.4.4 has been out for a couple of months and you might want to check the release notes to see if you might want to go to 7.4.4. (This should be a fairly painless upgrade.)
Bruno Wolff III wrote:
>
>7.4.4 has been out for a couple of months and you might want to check the
>release notes to see if you might want to go to 7.4.4. (This should be
>a fairly painless upgrade.)
>
>
I think you mean 7.4.3
Btw, shall i make dump and restore when upgrading 7.4.2 => 7.4.3 or
overwriting the binaries simply will do?
Mage
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Fri, 30 Jul 2004, Mage wrote:
> Btw, shall i make dump and restore when upgrading 7.4.2 => 7.4.3 or
> overwriting the binaries simply will do?
Yep, minor version upgrades do not need a dump/reload (except 7.4.0 ->
7.4.1 AFAIR).
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBCnOWtl86P3SPfQ4RAvqPAJ9Pbvh+UCIBj+J4JH3Cn2UyJcqwfgCaAtlj
0YBNMxF81vkAt82E21aV9xA=
=Edy8
-----END PGP SIGNATURE-----
Devrim GUNDUZ wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>
>Hi,
>
>On Fri, 30 Jul 2004, Mage wrote:
>
>
>
>>Btw, shall i make dump and restore when upgrading 7.4.2 => 7.4.3 or
>>overwriting the binaries simply will do?
>>
>>
>
>Yep, minor version upgrades do not need a dump/reload (except 7.4.0 ->
>7.4.1 AFAIR).
>
>
As far as I remember, the 7.4.1 => 7.4.2 also needed that. Correct me if
I'm wrong.
Mage
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, On Fri, 30 Jul 2004, Mage wrote: > >Yep, minor version upgrades do not need a dump/reload (except 7.4.0 -> > >7.4.1 AFAIR). > > > As far as I remember, the 7.4.1 => 7.4.2 also needed that. Correct me if > I'm wrong. You're right, I'm wrong: http://developer.postgresql.org/docs/postgres/release-7-4-2.html Regards, - -- Devrim GUNDUZ devrim~gunduz.org devrim.gunduz~linux.org.tr http://www.tdmsoft.com http://www.gunduz.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBCnXptl86P3SPfQ4RAuHJAJ9xLxit0/xTgle1RrPw1bKO+lPmBgCfT1io O00Yg7d45wzf3VoNR25uFJA= =6ORD -----END PGP SIGNATURE-----
On Fri, Jul 30, 2004 at 18:08:33 +0200, Mage <mage@mage.hu> wrote: > Bruno Wolff III wrote: > > > > >7.4.4 has been out for a couple of months and you might want to check the > >release notes to see if you might want to go to 7.4.4. (This should be > >a fairly painless upgrade.) > > > > > I think you mean 7.4.3 Sorry I have one instance running with a couple of post 7.4.3 changes (7.4 stable CVS) that will appear in 7.4.4 if and when it is released and I misremembered that as 7.4.4 having been released. > > Btw, shall i make dump and restore when upgrading 7.4.2 => 7.4.3 or > overwriting the binaries simply will do? You do NOT have to do a dump and restore when going from 7.4.2 to 7.4.3 as long as you build 7.4.3 the same way you did 7.4.2. You want some sort of backup in case something happens during the upgrade, but you shouldn't need to use it.
On Fri, Jul 30, 2004 at 18:16:37 +0200, Mage <mage@mage.hu> wrote: > > > As far as I remember, the 7.4.1 => 7.4.2 also needed that. Correct me if > I'm wrong. There have been cases where you didn't get all of the fixes without either doing an initdb or messing with the catalog tables, but you could still do the upgrade if you didn't need the fixes. For the 7.4.1 -> 7.4.2 upgrade the release notes detailed how to change the catalogs to take full advantage of the upgrade without having to do a dump and restore.