From: Scott Marlowe <scott.marlowe@gmail.com>
To: Decibel! <decibel@decibel.org>
Cc: Carol Walter <walterc@indiana.edu>
Cc: pgsql-admin@postgresql.org
Subject: Re: After upgrade cleanup
Date: Tue, 1 Jul 2008 13:54:35 -0600
Message-ID: <dcc563d10807011254r7c515bdao22045ee744eb14aa@mail.gmail.com> (raw)
In-Reply-To: <E199F56A-1571-4A52-88C0-568C519D87BE@decibel.org>
References: <A928C903-65D3-4F8D-930C-45E202C7F480@indiana.edu>
<E199F56A-1571-4A52-88C0-568C519D87BE@decibel.org>
On Fri, Jun 20, 2008 at 3:19 PM, Decibel! <decibel@decibel.org> wrote:
> On Jun 19, 2008, at 8:13 AM, Carol Walter wrote:
>>
>> I just did an upgrade from 8.1 to 8.2.3. We'll go up to 8.3.3 very soon,
>> but for reasons I won't go into, this intermediate step was necessary. My
>> problem is, now that the upgrade is done, how can I clean up the database
>> from the old version. I leave the original database up as long as I can
>> when I do an upgrade just in case I need to revert to it. Now I have the
>> databases from two versions on my server and I need to get rid of the old
>> one. Can I just remove the old files from the data directories? With other
>> systems, I've had trouble removing database files because upgrades use
>> certain files from old versions. I don't want to break my new database.
>> I'm on Solaris 10.
>
>
> Not only does the new version not use files from the old, it doesn't even
> know it exists. You can just nuke all the 8.1 stuff.
If you're paranoid, then you can also do:
sudo chmod 000 /old/data/dir
and see if anything breaks.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, decibel@decibel.org, walterc@indiana.edu
Subject: Re: After upgrade cleanup
In-Reply-To: <dcc563d10807011254r7c515bdao22045ee744eb14aa@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox