On Thu, October 16, 2008 06:47, Carol Walter wrote:
> Let me see if I understand this correctly.
> Always do a backup before doing any destructive sys admin functions. =)
> First, I run configure, taking care to make sure all the options point
> to the right places.
> Second, I run gmake
> Third, I run gmake install.
> On Oct 14, 2008, at 1:22 PM, Evan Rempel wrote:
>> 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
>> require a "sudo make install" if your install was done from
>> I hope this points you in mostly the right direction without begin
>> to long
>> Carol Walter wrote:
>>> 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,
>>> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
>>> To make changes to your subscription:
>> Evan Rempel erempel(at)uvic(dot)ca
>> Senior Programmer Analyst 250.721.7691
>> University Systems, University of Victoria
>> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
>> To make changes to your subscription:
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
As part of your backup, make sure you also backup your postgresql.conf and
pg_hba.conf if they are in your data directory. These are done at the
Operating System level using the cp (copy) command. They shouldn't be
overwritten, but having a backup copy of those is always nice for when
Timothy J. Bruce
visit my Website at: http://www.tbruce.com
Registered Linux User #325725
In response to
pgsql-admin by date
|Next:||From: Uwe Bartels||Date: 2008-10-17 10:25:37|
|Subject: refreshing prepared statements after index rebuild|
|Previous:||From: Carol Walter||Date: 2008-10-16 13:47:48|
|Subject: Re: Upgrade in same major version|