Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 0D48764FD91 for ; Tue, 14 Oct 2008 14:21:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 89056-03 for ; Tue, 14 Oct 2008 14:21:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from dog.comp.uvic.ca (dog.comp.uvic.ca [142.104.5.222]) by postgresql.org (Postfix) with ESMTP id 9816264FDA5 for ; Tue, 14 Oct 2008 14:21:27 -0300 (ADT) Received: from [142.104.191.242] (strike.comp.uvic.ca [142.104.191.242]) by dog.comp.uvic.ca (8.13.8/8.13.8) with ESMTP id m9EHLPeJ031267 for ; Tue, 14 Oct 2008 10:21:26 -0700 Message-ID: <48F4D515.3040902@uvic.ca> Date: Tue, 14 Oct 2008 10:21:25 -0700 From: Evan Rempel User-Agent: Thunderbird 1.5.0.12 (X11/20070530) MIME-Version: 1.0 To: "pgsql-admin@postgresql.org" Subject: Re: Upgrade in same major version References: <5A6C6B35-B5FF-4C4A-B976-A5B4522AB6B3@indiana.edu> In-Reply-To: <5A6C6B35-B5FF-4C4A-B976-A5B4522AB6B3@indiana.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-UVic-Virus-Scanned: OK - Passed virus scan by Sophos (sophie) on dog X-UVic-Spam-Scan: dog.comp.uvic.ca Not_scanned_LOCAL X-Scanned-By: MIMEDefang 2.63 on 142.104.5.91 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200810/105 X-Sequence-Number: 30561 What this means is that you do not have to "update" the data repository (wherever your postgresql database is stored). All that needs to be done is to uninstall the old version, and install the new version. Start the new version and use the data where it sits. Now, that all sound fine when I say it fast. There are a number of precautions that you may prefer to take, and the steps may differ significantly depending on your system. 1. Probably take a complete backup of your database should something go wrong. 2. Ensure that you have a way to "get back" to the previous version, or have a very reliable way to move forward, such as taking a pgdump that can be loaded back into the database, nearly regardless of version. 3. Your uninstall may be a package management step such as rpm, or you may just delete the files if your install was done from source. 4. Your install may be a package management step such as rpm, or you may require a "sudo make install" if your install was done from source. I hope this points you in mostly the right direction without begin to long winded. Evan. Carol Walter wrote: > Hello, > > I'm doing an upgrade from 8.2.4 to 8.2.10. The documentation says, > "When you update between compatible versions, you can simply replace > the executables and reuse the data directory on disk." I guess I > don't quite understand what this means. Replace them by running some > parts of the installation process? Replace them by copying them. > Are you talking about those files that usually reside in /usr/local/ > pgsql/bin and include psql and pg_ctl? > > I know these may seem like dumb questions to those of you who are old > hands at this. I'd be glad to read more documentation if there is > some that is more explicit than what I quoted above. > > Thanks so much, > > Carol > > -- > Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin -- Evan Rempel erempel@uvic.ca Senior Programmer Analyst 250.721.7691 University Systems, University of Victoria