Thread: Upgd from 7.0 to 7.1
Hi all, I'm in the planning to upgrade from 7.0 to 7.1 and need to ask a few questions before I make my deployment plan. Will I have to do a dump/restore of the database? I have a large database (100+ Million records) and would rather not have to do a dump. If I have to do a dump, do need to run the old db in order to do the dump. Then I guess I'd have to start the new db and do the restore. That would suck with a database this large. Please let me know about any details in doing this upgrade. Thanx, Mike Diehl, Network Monitoring Tool Devl. Sandia National Laboratories. (505) 284-3137 jdiehl@sandia.gov
I assume, then, that if I RTFM, I'll be able to figure out how to run two db's at the same time... I guess I have to run them in different directories? Or, do I do a dumpall, start the new server and do the restore? Which is the best method? Thanx, Mike Diehl, Network Monitoring Tool Devl. Sandia National Laboratories. (505) 284-3137 jdiehl@sandia.gov > -----Original Message----- > From: webb sprague [mailto:wsprague@o1.com] > Sent: May 29, 2001 10:52 AM > To: Diehl, Jeffrey > Subject: Re: [SQL] Upgd from 7.0 to 7.1 > > > Yes, you have to do a dump/restore. However, we have million > row databases > all over the place and pg_dump takes about 20 minutes with > 800 MhZ machine. > > You are right in that you need to dump running the old DB, > restore with the > new one. > > Enjoy. > W > > On Tuesday 29 May 2001 15:22, you wrote: > > Hi all, > > > > I'm in the planning to upgrade from 7.0 to 7.1 and need to ask a few > > questions before I make my deployment plan. > > > > Will I have to do a dump/restore of the database? I have a > large database > > (100+ Million records) and would rather not have to do a dump. > > > > If I have to do a dump, do need to run the old db in order > to do the dump. > > Then I guess I'd have to start the new db and do the > restore. That would > > suck with a database this large. > > > > Please let me know about any details in doing this upgrade. > > > > Thanx, > > Mike Diehl, > > Network Monitoring Tool Devl. > > Sandia National Laboratories. > > (505) 284-3137 > > jdiehl@sandia.gov > > > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 6: Have you searched our list archives? > > > > http://www.postgresql.org/search.mpl >
Yes, this is probably what I'll do. My drive is at 36% right now, so I should have enough. I also like haveing a back-out plan... Thanx, Mike Diehl, Network Monitoring Tool Devl. Sandia National Laboratories. (505) 284-3137 jdiehl@sandia.gov > -----Original Message----- > From: Thomas Swan [mailto:tswan-lst@ics.olemiss.edu] > Sent: May 29, 2001 4:41 PM > To: Diehl, Jeffrey > Cc: pgsql-sql@postgresql.org > Subject: Re: [SQL] Upgd from 7.0 to 7.1 > > > Jeffrey: > > dump_all the old DB (with the current version of postgres running) > stop the old postmaster > copy that DB directory (ie /var/lib/pgsql) to an alternate location > create a new directory for the location you want postgresql to run, > (i.e. the old location) > check the permissions on it... > start the new version of postgresql... > do the import (as postgres) ... > > I think that would be the best way to go about it. It's a lot easier > than sorting out multiple postmasters, ports, etc... > > If everything goes well, you should be up and running. If > not, you can > restore the old directory and run the old backend... > > Hope this helps... > > Thomas > > > > Diehl, Jeffrey wrote: > > >I assume, then, that if I RTFM, I'll be able to figure out > how to run two > >db's at the same time... I guess I have to run them in different > >directories? Or, do I do a dumpall, start the new server and do the > >restore? Which is the best method? > > > >Thanx, > >Mike Diehl, > >Network Monitoring Tool Devl. > >Sandia National Laboratories. > >(505) 284-3137 > >jdiehl@sandia.gov > > > > >
Jeffrey: dump_all the old DB (with the current version of postgres running) stop the old postmaster copy that DB directory (ie /var/lib/pgsql) to an alternate location create a new directory for the location you want postgresql to run, (i.e. the old location) check the permissions on it... start the new version of postgresql... do the import (as postgres) ... I think that would be the best way to go about it. It's a lot easier than sorting out multiple postmasters, ports, etc... If everything goes well, you should be up and running. If not, you can restore the old directory and run the old backend... Hope this helps... Thomas Diehl, Jeffrey wrote: >I assume, then, that if I RTFM, I'll be able to figure out how to run two >db's at the same time... I guess I have to run them in different >directories? Or, do I do a dumpall, start the new server and do the >restore? Which is the best method? > >Thanx, >Mike Diehl, >Network Monitoring Tool Devl. >Sandia National Laboratories. >(505) 284-3137 >jdiehl@sandia.gov >