X-Original-To: pgsql-general-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D832F564E1 for ; Sun, 27 Feb 2005 03:07:09 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 93561-09 for ; Sun, 27 Feb 2005 03:07:01 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id B2EFA52A9B for ; Sun, 27 Feb 2005 03:07:07 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j1R371wq094112 for ; Sun, 27 Feb 2005 03:07:01 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j1R2noxi087709 for pgsql-general@postgresql.org; Sun, 27 Feb 2005 02:49:50 GMT (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.general Subject: Re: postgresql 8.0 advantages Date: Sat, 26 Feb 2005 21:12:54 -0500 Organization: cbbrowne Computing Inc Lines: 38 Message-ID: References: <421F3926.6090201@graciousstyle.com> <5708.1109348115@sss.pgh.pa.us> <421F5E5D.1010902@graciousstyle.com> <1109410075.4089.216.camel@jeff> <20050226213527.GA84483@decibel.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:69voSQFoBtB0dUby0cDuA0If10k= To: pgsql-general@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200502/1415 X-Sequence-Number: 74219 The world rejoiced as decibel@decibel.org ("Jim C. Nasby") wrote: > On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote: >> On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote: >> > Thanks! >> > >> > Is there any documentation on how to upgrade to 8.0? >> > >> > Is it possible to upgrade from 7.4 to 8.0 while keeping a production >> > database running "in place"? Or should I install 8.0 in another >> > directory/machine and then restore the database into it? Are there any >> > incompatibilities/modifications to databases from the earlier veresion >> > required? >> > >> >> You might want to check out Slony-I for the >> purpose of upgrading. Slony is actually a replication engine, but it can >> be used to upgrade with little or no downtime. Otherwise, just >> dump/upgrade/restore like normal. > > Has anyone tried moving a database from one location to another on the > HD? I'd like to use slony to minimize downtime, but I'd also like my > data to end up in the same place it is right now when I'm done. Yes, that certainly ought to work. If what you're meaning is that you make a replica that sits in /opt/VERSION8, and then, once the upgrade is complete, rename that to /opt/MYDATABASE which was where your version 7.4 DB used to be. We have copied databases from one server to another by copying the files; making it work was as easy as making sure we ran "pg_ctl -D $RIGHT_DIRECTORY start" :-). -- let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;; http://cbbrowne.com/info/lisp.html "I don't know why, but first C programs tend to look a lot worse than first programs in any other language (maybe except for FORTRAN, but then I suspect all FORTRAN programs look like `firsts')" -- Olaf Kirch