Hi Tino, That was what we suspected and in fact didn't want to run any unnecessary risks. Thanks again.
James. On 5/12/08, Tino Schwarze <[EMAIL PROTECTED]> wrote: > > Hi James, > > On Mon, May 12, 2008 at 09:25:34AM +0200, James Farrugia wrote: > > > First of all thanks for the immediate replies! > > Was actually waiting for the right moment to upgrade to 8.3 but > migrating a > > live 1Tb database is a bit daunting especially if you have never done it > > before (as in my case). If I'm not mistaken i can upgrade to the latest > > minor version without having to dump and restore so I'll do that. > > You need to check the release notes of the particulra minor release you > are upgrading to. Some minor releases also require a dump/restore cycle > because of bugfixes. You're lucky: 8.2.7 doesn't require dump/restore in > your case, the release notes say: > "A dump/restore is not required for those running 8.2.X" > > > One last thing...can we run into data-loss problems with successfully > > vacuumed tables even if there is one unvacuumed database object; what > would > > have happened if I ignored to vacuum that rogue pg_toast (which was the > only > > unvacuumed object within the entire database)? > > At a certain point, the server would have switched to "emergency mode" > and wouldn't have accepted any commands any more. See the description > here: > > http://www.postgresql.org/docs/8.2/static/routine-vacuuming.html#VACUUM-FOR-WRAPAROUND > > HTH, > > Tino. > > -- > "What we resist, persists." (Zen saying) > > www.craniosacralzentrum.de > www.forteego.de > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin >
